Triple
T4174284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Brother Island |
E86437
|
entity |
| Predicate | builtStructureCondition |
P25131
|
FINISHED |
| Object | ruins |
—
|
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: ruins | Statement: [North Brother Island, builtStructureCondition, ruins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtStructureCondition Context triple: [North Brother Island, builtStructureCondition, ruins]
-
A.
buildingCondition
chosen
Indicates the physical state or quality of a building, such as how well it is preserved, maintained, or structurally sound.
-
B.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
C.
constructionType
Indicates the specific method or style by which something is built or constructed.
-
D.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
E.
builtProperty
Indicates that a constructed structure or building has been created on, or is associated with, a particular property or piece of land.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.