Triple
T24668302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Joplin tornado |
E610747
|
entity |
| Predicate | pathWidth |
P156946
|
FINISHED |
| Object | up to 1 mile |
—
|
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 1 mile | Statement: [2011 Joplin tornado, pathWidth, up to 1 mile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pathWidth Context triple: [2011 Joplin tornado, pathWidth, up to 1 mile]
-
A.
footpathWidth
Indicates the measured or designated width of a footpath in the context of a spatial or infrastructural relationship.
-
B.
trackWidth
Indicates the lateral distance between two parallel tracks or wheels, typically measured from center to center.
-
C.
roadWidth
Indicates the measured breadth or distance across a road, typically from one edge or curb to the opposite edge or curb.
-
D.
basePathLength
Indicates the length of the primary or reference path used as a baseline in a given context.
-
E.
pathLenConstraint
Indicates a restriction on the allowable length of a path between entities, such as limiting the number of steps, distance, or hops in a connection.
- F. None of above. chosen
Provenance (4 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f41010f06c81908ee7f773220df14f |
completed | May 1, 2026, 2:29 a.m. |
Created at: April 18, 2026, 2:41 a.m.