Triple
T789193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 4 Sheppard |
E16872
|
entity |
| Predicate | hasSystemLength |
P14300
|
FINISHED |
| Object | approximately 5.5 km |
—
|
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 5.5 km | Statement: [Line 4 Sheppard, hasSystemLength, approximately 5.5 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSystemLength Context triple: [Line 4 Sheppard, hasSystemLength, approximately 5.5 km]
-
A.
isFeatureLength
Indicates that something (typically a film or video) has a duration long enough to be considered a full-length, standard feature.
-
B.
hasMainSpanLength
Indicates the relationship specifying the primary or main span’s length associated with an entity.
-
C.
hasWeekLength
Indicates the duration of a week associated with an entity, typically expressed as a number of days.
-
D.
supportsKeyLength
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
-
E.
hasTrailLength
chosen
Indicates that an entity (such as a trail or route) has a specific measured length.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7841b0c8190859ecd247e32c6ec |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.