Triple
T29551214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 97 |
E749770
|
entity |
| Predicate | isShortForSystem |
P167017
|
FINISHED |
| Object | Interstate Highway System route length spectrum |
—
|
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: Interstate Highway System route length spectrum | Statement: [Interstate 97, isShortForSystem, Interstate Highway System route length spectrum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShortForSystem Context triple: [Interstate 97, isShortForSystem, Interstate Highway System route length spectrum]
-
A.
isShortName
Indicates that one name is an abbreviated or shorter form of another name.
-
B.
isShortForClass
Indicates that one class name is an abbreviation or shortened form of another class name.
-
C.
isShort
Indicates that one entity has a relatively small height, length, or duration compared to a standard or to other entities.
-
D.
hasShort
Indicates that an entity possesses or is characterized by something of short length or duration.
-
E.
isShortSurname
Indicates that a person's surname is considered short in length, typically based on having few characters.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cf7741881908a2c2fa041066a0c |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6642e676c8190af0e6b1416eed6d2 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 5:12 p.m.