Triple
T37297973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New London Harbor Light |
E925855
|
entity |
| Predicate | yearCurrentStructureBuilt |
P32863
|
FINISHED |
| Object | 1801 |
—
|
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: 1801 | Statement: [New London Harbor Light, yearCurrentStructureBuilt, 1801]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearCurrentStructureBuilt Context triple: [New London Harbor Light, yearCurrentStructureBuilt, 1801]
-
A.
yearBuilt
Indicates the specific year in which something (typically a structure or object) was constructed or completed.
-
B.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
C.
superstructureConstructedIn
Indicates that the construction of a superstructure took place at, within, or during a specified location, context, or time.
-
D.
currentTowerCompletedYear
chosen
Indicates the year in which the currently existing or latest version of the tower was completed.
-
E.
oldestBuildingDate
Indicates the calendar date on which the earliest or first-constructed building in a given set or area was built or completed.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.