Triple
T22467997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 57 |
E555409
|
entity |
| Predicate | numericDesignationType |
P70157
|
FINISHED |
| Object | odd-numbered Interstate |
—
|
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: odd-numbered Interstate | Statement: [Interstate 57, numericDesignationType, odd-numbered Interstate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericDesignationType Context triple: [Interstate 57, numericDesignationType, odd-numbered Interstate]
-
A.
hasDesignationNumber
Indicates that an entity is associated with a specific official designation or identification number.
-
B.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
C.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
D.
letterOrNumberDesignation
chosen
Indicates that something is identified or labeled using a specific letter, number, or combination of both.
-
E.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15bdda62c8190937ac13a4481b4b7 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.