Triple
T38398691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elberon station |
E900834
|
entity |
| Predicate | adjacentLineDirectionSouth |
P194508
|
FINISHED |
| Object | toward Asbury Park and Bay Head |
—
|
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: toward Asbury Park and Bay Head | Statement: [Elberon station, adjacentLineDirectionSouth, toward Asbury Park and Bay Head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentLineDirectionSouth Context triple: [Elberon station, adjacentLineDirectionSouth, toward Asbury Park and Bay Head]
-
A.
lineDirectionSouth
Indicates that a line or path is oriented or directed toward the south.
-
B.
adjacentStationTowardsSouth
Indicates that one station is directly next to another in the southward direction along a route or line.
-
C.
adjacentLine
Indicates that one line is directly next to another line, sharing a common boundary or position without overlapping.
-
D.
adjacentStationSouth
Indicates that one station is directly to the south of another station, with no other station in between.
-
E.
adjacentCitySouth
Indicates that one city is directly to the south of another city, sharing a common boundary or being immediately neighboring in that direction.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69fd76d0d7608190b350336d6c18182d |
completed | May 8, 2026, 5:38 a.m. |
Created at: May 3, 2026, 4:31 p.m.