Triple
T161586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 395 |
E3297
|
entity |
| Predicate | followsNumberingScheme |
P3378
|
FINISHED |
| Object | three-digit Interstate numbering |
—
|
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: three-digit Interstate numbering | Statement: [Interstate 395, followsNumberingScheme, three-digit Interstate numbering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsNumberingScheme Context triple: [Interstate 395, followsNumberingScheme, three-digit Interstate numbering]
-
A.
numberingType
chosen
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
B.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
C.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
D.
hasNumberCategory
Indicates that an entity is associated with a specific numerical classification or type.
-
E.
beganOfficialNumberingWith
Indicates that an entity started its formal or official numbering sequence with a specified initial number or identifier.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2585877648190a2ec320182a69343 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256623704819089d9eeefe05858ce |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.