Triple
T37352303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exit 5 (Newington, New Hampshire) |
E927357
|
entity |
| Predicate | isNumberedExitOn |
P117800
|
FINISHED |
| Object | Spaulding Turnpike |
—
|
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: Spaulding Turnpike | Statement: [Exit 5 (Newington, New Hampshire), isNumberedExitOn, Spaulding Turnpike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberedExitOn Context triple: [Exit 5 (Newington, New Hampshire), isNumberedExitOn, Spaulding Turnpike]
-
A.
hasNumberedExit
chosen
Indicates that an entity (such as a road or highway) includes or is associated with an exit that has an assigned number.
-
B.
hasNumberOfExits
Indicates the relationship that specifies how many exits are associated with a given entity.
-
C.
isExitPointFrom
Indicates that something serves as the location or point through which an entity departs or leaves from another entity or area.
-
D.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
E.
exitsThrough
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.