Triple
T14267979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Hoboken, New Jersey |
E353699
|
entity |
| Predicate | relativeDirectionFrom |
P23578
|
FINISHED |
| Object | west of Hoboken, New Jersey |
—
|
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: west of Hoboken, New Jersey | Statement: [West Hoboken, New Jersey, relativeDirectionFrom, west of Hoboken, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeDirectionFrom Context triple: [West Hoboken, New Jersey, relativeDirectionFrom, west of Hoboken, New Jersey]
-
A.
directionRelativeTo
Indicates the spatial orientation of one entity in relation to another, such as which way it faces or points relative to a reference entity.
-
B.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
D.
directionRelativeToARP
Indicates the spatial direction or orientation of an entity relative to a specified Aircraft Reference Point (ARP).
-
E.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6358c2288190ac1fd26e688a605d |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.