Triple
T9656171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Route 9 family |
E233456
|
entity |
| Predicate | usesDesignationPattern |
P89449
|
FINISHED |
| Object | number-plus-letter suffix |
—
|
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: number-plus-letter suffix | Statement: [New York State Route 9 family, usesDesignationPattern, number-plus-letter suffix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDesignationPattern Context triple: [New York State Route 9 family, usesDesignationPattern, number-plus-letter suffix]
-
A.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
-
B.
usesServiceDesignation
Indicates that one entity adopts or applies a particular service designation associated with another entity or offering.
-
C.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
D.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
E.
canBeDesignatedBy
Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
- 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_69ca848c1ba88190b84b410cd14627fc |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bdd5c0c8190a6c82a1609454d1b |
completed | April 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:14 p.m.