Triple
T5147191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z |
E116100
|
entity |
| Predicate | division |
P889
|
FINISHED |
| Object | BMT |
E78743
|
NE 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: BMT | Statement: [Z, division, BMT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BMT Context triple: [Z, division, BMT]
-
A.
BMT
chosen
BMT (Brooklyn–Manhattan Transit Corporation) was a major private New York City subway operator whose lines now form one of the primary divisions of the modern NYC Subway system.
-
B.
BMT lines
BMT lines are a group of New York City Subway routes that originated with the former Brooklyn–Manhattan Transit Corporation and primarily serve Brooklyn and Manhattan.
-
C.
BAM
BAM is a renowned multi-arts center in Brooklyn, New York, known for its innovative programming in theater, dance, music, opera, and film.
-
D.
MRT
MRT is the three-letter ISO 3166-1 alpha-3 country code assigned to Mauritania.
-
E.
MRT
MRT is the commonly used abbreviation for the Taipei Metro, the rapid transit system serving Taipei and its surrounding areas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78afc32081909fd4de3dbf31ea3a |
completed | March 20, 2026, 4:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69becffa6a2881908f4b1ef85bdcce30 |
completed | March 21, 2026, 5:06 p.m. |
Created at: March 20, 2026, 1:43 p.m.