Triple
T16301652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 91 |
E395803
|
entity |
| Predicate | usedAsDesignationFor |
P6238
|
FINISHED |
| Object | numbered state highways |
—
|
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: numbered state highways | Statement: [SR 91, usedAsDesignationFor, numbered state highways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsDesignationFor Context triple: [SR 91, usedAsDesignationFor, numbered state highways]
-
A.
usedAsSelfDesignation
Indicates that an entity is used by a person or group as a term to refer to or identify themselves.
-
B.
usesServiceDesignation
Indicates that one entity adopts or applies a particular service designation associated with another entity or offering.
-
C.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
D.
designationUse
Indicates how a particular designation or title is intended to be used or applied in relation to an entity.
-
E.
designationUsedFor
chosen
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e32da7081908d8bd320374a5731 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.