Triple
T15663840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biloxi Bay Bridge |
E376634
|
entity |
| Predicate | predecessorDamagedIn |
P992
|
FINISHED |
| Object | August 2005 |
—
|
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: August 2005 | Statement: [Biloxi Bay Bridge, predecessorDamagedIn, August 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorDamagedIn Context triple: [Biloxi Bay Bridge, predecessorDamagedIn, August 2005]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
C.
bearerPredecessor
Indicates that one entity previously held a role, title, or position that is now held by another entity, establishing a predecessor-successor relationship between them.
-
D.
damagedIn
chosen
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
-
E.
predecessorStatus
Indicates that one entity’s status is determined by, or directly follows from, the status of a preceding entity in a sequence or process.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f0e2668819092e52712cddd0721 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.