Triple
T12113735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mills at Jersey Gardens |
E288500
|
entity |
| Predicate | nearExit |
P99467
|
FINISHED |
| Object | Exit 13A of the New Jersey Turnpike |
—
|
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: Exit 13A of the New Jersey Turnpike | Statement: [The Mills at Jersey Gardens, nearExit, Exit 13A of the New Jersey Turnpike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearExit Context triple: [The Mills at Jersey Gardens, nearExit, Exit 13A of the New Jersey Turnpike]
-
A.
near
Indicates that one entity is located at a short distance from another entity in space or position.
-
B.
hasNearbyExit
chosen
Indicates that one entity has an exit located close to it in space or distance.
-
C.
nearPass
Indicates that one entity moves or travels close to another entity without necessarily making direct contact or interaction.
-
D.
nearestEntrance
Indicates that one entrance is the closest access point to a given location or entity compared to all other possible entrances.
-
E.
nearBorderBetween
Indicates that something is located close to the dividing line or boundary shared between two adjacent areas or regions.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.