Triple
T5502507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newburgh–Beacon Ferry |
E144360
|
entity |
| Predicate | terminalAtBeacon |
P43881
|
FINISHED |
| Object | near Beacon station |
—
|
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: near Beacon station | Statement: [Newburgh–Beacon Ferry, terminalAtBeacon, near Beacon station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalAtBeacon Context triple: [Newburgh–Beacon Ferry, terminalAtBeacon, near Beacon station]
-
A.
transmitterLocation
Indicates the spatial position or place where a transmitter is situated or operates.
-
B.
terminusBState
Indicates the state or condition of the entity that serves as the endpoint (B terminus) of a connection, process, or relationship.
-
C.
locatedAtTerminusOf
chosen
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
-
D.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
E.
terminalName
Indicates the name or label assigned to a specific terminal or endpoint within a system or network.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0bbea48190bb6fecaee9c0b1d0 |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.