Triple
T38022264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 104th Street station |
E948670
|
entity |
| Predicate | formerSystem |
P147859
|
FINISHED |
| Object | BMT Fulton Street Line |
—
|
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: BMT Fulton Street Line | Statement: [104th Street station, formerSystem, BMT Fulton Street Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerSystem Context triple: [104th Street station, formerSystem, BMT Fulton Street Line]
-
A.
previousSystemName
Indicates that an entity was formerly known by a different system name prior to its current designation.
-
B.
formerProgram
Indicates that an entity previously held the role or status of a program but no longer does so.
-
C.
formerType
Indicates that one entity previously had a certain type, role, or classification but no longer does.
-
D.
previouslyUsedSystem
chosen
Indicates that an entity made use of a particular system at some time in the past, prior to the current context or state.
-
E.
replacedEarlierSystems
Indicates that one system has taken the place of and superseded other systems that existed or were in use before it.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a012efebda88190a90c8f650e4b1ee9 |
completed | May 11, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_6a01298cc604819087c836659c128926 |
completed | May 11, 2026, 12:57 a.m. |
Created at: May 3, 2026, 4:20 p.m.