Triple
T11793407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koror–Babeldaob Bridge |
E280443
|
entity |
| Predicate | collapsed |
P4060
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Koror–Babeldaob Bridge, collapsed, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collapsed Context triple: [Koror–Babeldaob Bridge, collapsed, 1996]
-
A.
collapsedAfter
Indicates that one entity collapsed at some point in time after another specified event or entity’s collapse.
-
B.
collapsedOn
Indicates that one entity physically fell or caved in onto another entity, ending up resting on or covering it.
-
C.
collapsedDueTo
Indicates that one entity fell down, caved in, or structurally failed as a result of another specified cause or factor.
-
D.
collapsedWith
Indicates that one entity fell down or caved in together with another entity, typically as part of the same collapse event.
-
E.
collapsedDuring
chosen
Indicates that one entity structurally failed or fell down while another specified event or process was occurring.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a082d08190a42541396a06ed98 |
completed | April 10, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.