Triple
T26852505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 43 |
E676095
|
entity |
| Predicate | usedAsHiddenDesignationFor |
P75661
|
FINISHED |
| Object | U.S. Route 301 in Florida |
—
|
NE NERFINISHED |
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: U.S. Route 301 in Florida | Statement: [SR 43, usedAsHiddenDesignationFor, U.S. Route 301 in Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsHiddenDesignationFor Context triple: [SR 43, usedAsHiddenDesignationFor, U.S. Route 301 in Florida]
-
A.
hasInternalDesignationFor
chosen
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
B.
usedAsSelfDesignation
Indicates that an entity is used by a person or group as a term to refer to or identify themselves.
-
C.
protectedDesignation
Indicates that one entity has an officially recognized and legally protected designation or status in relation to another entity.
-
D.
usesServiceDesignation
Indicates that one entity adopts or applies a particular service designation associated with another entity or offering.
-
E.
isDeprecatedDesignation
Indicates that a particular designation or label is no longer current or recommended for use.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 5:18 a.m.