Triple
T31844891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J (New York City Subway service) |
E812910
|
entity |
| Predicate | southernTerminalBorough |
P49613
|
FINISHED |
| Object | Manhattan |
—
|
NE NERFINISHED |
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: Manhattan | Statement: [J (New York City Subway service), southernTerminalBorough, Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: southernTerminalBorough Context triple: [J (New York City Subway service), southernTerminalBorough, Manhattan]
-
A.
terminusBorough
chosen
Indicates the borough in which the endpoint or terminus of something (such as a route or line) is located.
-
B.
terminusSouthNear
Indicates that the southern end or terminus of one entity is located close to another entity.
-
C.
southernTerminusVariant
Indicates a variant or alternative form of the southern endpoint or terminus of something (such as a route, line, or boundary).
-
D.
terminusCitySouth
Indicates that something serves as the southern terminus or endpoint located in a particular city.
-
E.
hasSouthernTerminus
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b03577f88190a30e05f3aa0110c6 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:50 p.m.