Triple
T4460373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chenab Rail Bridge |
E98236
|
entity |
| Predicate | designedForWindSpeed |
P20750
|
FINISHED |
| Object | up to 266 km/h |
—
|
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: up to 266 km/h | Statement: [Chenab Rail Bridge, designedForWindSpeed, up to 266 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForWindSpeed Context triple: [Chenab Rail Bridge, designedForWindSpeed, up to 266 km/h]
-
A.
designedToWithstand
chosen
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
-
B.
designPowerOutput
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
C.
windResistance
Indicates the degree to which an entity opposes or reduces the effect of wind acting upon it.
-
D.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
E.
maximumSustainedWinds
Indicates the highest wind speed that is maintained continuously over a specified averaging period, rather than in brief gusts.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35673337c8190b923159791ec27e3 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.