Triple
T6086484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Trafalgar |
E135650
|
entity |
| Predicate | lighthouseConstructionYear |
P64263
|
FINISHED |
| Object | 1860 |
—
|
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: 1860 | Statement: [Cape Trafalgar, lighthouseConstructionYear, 1860]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lighthouseConstructionYear Context triple: [Cape Trafalgar, lighthouseConstructionYear, 1860]
-
A.
lighthouseConstructedIn
chosen
Indicates that a lighthouse was built or established during a specific time period or in a specific year.
-
B.
churchConstructionDate
Indicates the date on which a church was constructed or originally built.
-
C.
lighthouseStatus
Indicates the operational condition or state (e.g., active, inactive, under maintenance) of a lighthouse at a given time.
-
D.
lighthouseRebuilt
Indicates that a lighthouse, previously existing, has been reconstructed or built again after damage, destruction, or decommissioning.
-
E.
isOldestLighthouseOn
Indicates that one lighthouse is the oldest existing lighthouse located on a specified landmass or geographic area.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0578a8b8081908490e447ae3419f9 |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.