Triple
T29437689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 375 |
E746623
|
entity |
| Predicate | designationEvent |
P18722
|
FINISHED |
| Object | named Extraterrestrial Highway by the State of Nevada |
—
|
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: named Extraterrestrial Highway by the State of Nevada | Statement: [SR 375, designationEvent, named Extraterrestrial Highway by the State of Nevada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designationEvent Context triple: [SR 375, designationEvent, named Extraterrestrial Highway by the State of Nevada]
-
A.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
B.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
C.
namedForEventAssociatedWithHonoree
Indicates that something is named in recognition of an event that is closely associated with the honoree.
-
D.
namedForEventDate
Indicates that something is named after or in reference to the date on which a particular event occurred.
-
E.
designationAct
chosen
Indicates an official act by which an authority formally assigns, names, or appoints an entity to a specific role, status, or function.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 28, 2026, 3:18 p.m.