Triple
T20393013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Disappointment Lighthouse |
E500128
|
entity |
| Predicate | 19thCenturyStructure |
P62809
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cape Disappointment Lighthouse, 19thCenturyStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 19thCenturyStructure Context triple: [Cape Disappointment Lighthouse, 19thCenturyStructure, true]
-
A.
builtIn19thCentury
chosen
Indicates that something was constructed during the 19th century.
-
B.
constructionCentury
Indicates the century during which something was constructed or built.
-
C.
locatedInBuildingConstructedInCentury
Indicates that something is located in a building whose construction dates to a specified century.
-
D.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
E.
architectOf19thCenturyReconstruction
Indicates that one entity served as the architect responsible for the reconstruction of another entity during the 19th century.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6791144788190a0ab42cf0141b6a3 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.