Triple
T26431257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WA 99 |
E664514
|
entity |
| Predicate | containsFormerStructure |
P52639
|
FINISHED |
| Object | Alaskan Way Viaduct |
—
|
NE NERFINISHED |
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: Alaskan Way Viaduct | Statement: [WA 99, containsFormerStructure, Alaskan Way Viaduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFormerStructure Context triple: [WA 99, containsFormerStructure, Alaskan Way Viaduct]
-
A.
containsStructureFrom
chosen
Indicates that one entity includes or incorporates a structural component originating from another entity.
-
B.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
C.
hasPredecessorStructureFrom
Indicates that one structure existed or was established before another structure in a sequential or developmental order.
-
D.
hasFormerParent
Indicates that an entity was previously the parent of another entity but no longer holds that parental role or status.
-
E.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 26, 2026, 11:49 p.m.