Triple
T14073835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Greenbrier |
E338678
|
entity |
| Predicate | bunkerConstructionEnd |
P112707
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [The Greenbrier, bunkerConstructionEnd, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bunkerConstructionEnd Context triple: [The Greenbrier, bunkerConstructionEnd, 1961]
-
A.
hasBunkers
Indicates that one entity possesses or contains bunkers, such as fortified shelters or storage structures, as part of its features or infrastructure.
-
B.
monumentConstructionEnd
Indicates the date or time at which the construction of a monument was completed.
-
C.
typicalConstructionEnd
Indicates the usual or expected point in time or stage at which a construction process or building project is completed.
-
D.
buildingEnd
Indicates the point or time at which the construction or existence of a building comes to a conclusion.
-
E.
bunkersPurpose
Indicates that one entity serves as the purpose, function, or intended use of a bunker or group of bunkers.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5bc49881909012b66fa451f495 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:21 p.m.