Triple
T13599279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddystone Rocks |
E324900
|
entity |
| Predicate | thirdLighthouseCompletion |
P110247
|
FINISHED |
| Object | 1759 |
—
|
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: 1759 | Statement: [Eddystone Rocks, thirdLighthouseCompletion, 1759]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdLighthouseCompletion Context triple: [Eddystone Rocks, thirdLighthouseCompletion, 1759]
-
A.
hasLightHouse
Indicates that one place or structure possesses, contains, or is associated with a lighthouse.
-
B.
lighthouseRebuilt
Indicates that a lighthouse, previously existing, has been reconstructed or built again after damage, destruction, or decommissioning.
-
C.
towerCompletedBefore
Indicates that the construction or completion of one tower occurred earlier in time than the construction or completion of another tower.
-
D.
lighthouseStatus
Indicates the operational condition or state (e.g., active, inactive, under maintenance) of a lighthouse at a given time.
-
E.
isFirstLighthouseIn
Indicates that a lighthouse is the earliest or first one established within a specified location or region.
- F. None of above. chosen
Provenance (4 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0795acc8190a08667ab9dcb0d44 |
completed | April 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf9f3bdc8190838539aaef1f422b |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:49 p.m.