Triple
T894552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thacher Island |
E19313
|
entity |
| Predicate | isListedAs |
P1278
|
FINISHED |
| Object | historic maritime site |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: historic maritime site | Statement: [Thacher Island, isListedAs, historic maritime site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isListedAs Context triple: [Thacher Island, isListedAs, historic maritime site]
-
A.
listedOn
chosen
Indicates that an item, entity, or piece of information appears as an entry on a particular list, platform, or catalog.
-
B.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
C.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad22b6fc819093e655c8ce1f738b |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.