Triple
T30853976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Gate Bridge collapse |
E785863
|
entity |
| Predicate | sectionWeight |
P1575
|
FINISHED |
| Object | approximately 2000 tonnes |
—
|
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: approximately 2000 tonnes | Statement: [West Gate Bridge collapse, sectionWeight, approximately 2000 tonnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionWeight Context triple: [West Gate Bridge collapse, sectionWeight, approximately 2000 tonnes]
-
A.
وزن
Indicates a relationship where one entity has, measures, or is characterized by a certain weight or mass.
-
B.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
C.
sectorWeighting
Indicates the proportion or emphasis assigned to a particular sector within a broader portfolio, index, or classification.
-
D.
statutoryWeight
Indicates that something has a legally defined or mandated weight specified by statute or regulation.
-
E.
weight
chosen
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6917eb3c08190a435aa82aea53809 |
completed | May 3, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:46 p.m.