Triple
T1320819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shore Line East |
E28212
|
entity |
| Predicate | zoneNumberingDirection |
P16737
|
FINISHED |
| Object | west-to-east from New Haven |
—
|
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-to-east from New Haven | Statement: [Shore Line East, zoneNumberingDirection, west-to-east from New Haven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneNumberingDirection Context triple: [Shore Line East, zoneNumberingDirection, west-to-east from New Haven]
-
A.
hasCountingDirection
chosen
Indicates the direction or order in which counting or enumeration proceeds between related entities.
-
B.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
C.
regionNumber
Indicates that an entity is assigned to or associated with a specific numbered region within a larger spatial or organizational division.
-
D.
roadNumberingZone
Indicates the designated numbering zone or area within which a particular road’s identification or route number is assigned.
-
E.
clockChangeDirection
Indicates a change in the rotational or movement direction of a clock or clock-like mechanism.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c179883c8190b68fbeebb9696982 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.