Triple
T24668301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Joplin tornado |
E610747
|
entity |
| Predicate | pathLength |
P156945
|
FINISHED |
| Object | approximately 22.1 miles |
—
|
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 22.1 miles | Statement: [2011 Joplin tornado, pathLength, approximately 22.1 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pathLength Context triple: [2011 Joplin tornado, pathLength, approximately 22.1 miles]
-
A.
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.
-
B.
basePathLength
Indicates the length of the primary or reference path used as a baseline in a given context.
-
C.
dataPathLength
Indicates the length or distance of a specified data path within a data structure, system, or network.
-
D.
hasWalkingPathLength
Indicates the length or distance of a designated walking path associated with an entity.
-
E.
patternLength
Indicates the length or size of a recurring pattern associated with an entity or process.
- 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.