Triple
T13455512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IND/BMT Division |
E311220
|
entity |
| Predicate | hasInteroperableLines |
P109575
|
FINISHED |
| Object | former IND lines |
—
|
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: former IND lines | Statement: [IND/BMT Division, hasInteroperableLines, former IND lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteroperableLines Context triple: [IND/BMT Division, hasInteroperableLines, former IND lines]
-
A.
hasInterchangesWith
Indicates that two transportation routes, lines, or services share one or more points where passengers can transfer between them.
-
B.
hasStraightLines
Indicates that the related entity possesses or is characterized by straight, non-curved lines.
-
C.
hasDeFactoLine
Indicates that there exists an unofficial or non-legally recognized boundary or demarcation line functioning in practice between the related entities.
-
D.
hasCrossPlatformInterchange
Indicates that there is a transfer point where passengers can switch between different transportation platforms or modes within the same location.
-
E.
hasPlannedLine
Indicates that an entity is associated with a specific planned route or line intended for future or scheduled use.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaefc52448190b30d7999f44a9765 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadce235f88190a6433395d2969811 |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:41 p.m.