Triple
T21318016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuller Warren Bridge |
E525528
|
entity |
| Predicate | hasDesignLife |
P8105
|
FINISHED |
| Object | long-span highway bridge design |
—
|
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: long-span highway bridge design | Statement: [Fuller Warren Bridge, hasDesignLife, long-span highway bridge design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignLife Context triple: [Fuller Warren Bridge, hasDesignLife, long-span highway bridge design]
-
A.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
hasDesigned
Indicates that one entity is the creator or designer of another entity.
-
C.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
D.
designLifetime
chosen
Indicates the intended duration or operational period for which something is designed to function as specified.
-
E.
hasDesignPeriod
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dd1ce9c81908c373362254427bf |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:36 p.m.