Triple
T27076797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head Harbour (East Quoddy) Lighthouse |
E685484
|
entity |
| Predicate | hasYearOfCurrentTower |
P32863
|
FINISHED |
| Object | 1830s |
—
|
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: 1830s | Statement: [Head Harbour (East Quoddy) Lighthouse, hasYearOfCurrentTower, 1830s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYearOfCurrentTower Context triple: [Head Harbour (East Quoddy) Lighthouse, hasYearOfCurrentTower, 1830s]
-
A.
currentTowerCompletedYear
chosen
Indicates the year in which the currently existing or latest version of the tower was completed.
-
B.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
C.
hasTowerPosition
Indicates that an entity occupies or is assigned a specific position or location within a tower.
-
D.
yearCurrentTowerFirstLit
Indicates the calendar year in which the current tower was first illuminated or put into operation.
-
E.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623168bb081909bef37ad8920f65f |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:31 a.m.