Triple
T30089493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County Route 645 (Sussex County, New Jersey) |
E764687
|
entity |
| Predicate | stateHighwayNumberingApplies |
P162054
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [County Route 645 (Sussex County, New Jersey), stateHighwayNumberingApplies, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHighwayNumberingApplies Context triple: [County Route 645 (Sussex County, New Jersey), stateHighwayNumberingApplies, false]
-
A.
highwayNumberingStatus
chosen
Indicates the current designation or classification state of a highway within an official numbering system.
-
B.
highwayNumberingSystem
Indicates a system that assigns and organizes numerical designations to highways within a road network.
-
C.
nationalHighwayNetworkState
Indicates that a state is part of, or associated with, the national highway network.
-
D.
stateHighwayDesignationIn
Indicates that a roadway has been designated as a state highway within a specified jurisdiction or region.
-
E.
highwayNumberingScheme
Indicates the system or method by which highways are assigned their route numbers or designations.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 29, 2026, 7:05 p.m.