Triple
T4562976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winslow Junction–Atlantic City route |
E121838
|
entity |
| Predicate | hasEndpointType |
P57698
|
FINISHED |
| Object | junction |
—
|
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: junction | Statement: [Winslow Junction–Atlantic City route, hasEndpointType, junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndpointType Context triple: [Winslow Junction–Atlantic City route, hasEndpointType, junction]
-
A.
hasPortType
Indicates that an entity is associated with, or characterized by, a specific type or category of port.
-
B.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
C.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
D.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
E.
hasEnvironmentType
Indicates that an entity is associated with or occurs within a specific type or category of environment.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd5830b4308190a63699bf28922375 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:09 p.m.