Triple
T8224300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMT lines |
E192138
|
entity |
| Predicate | usesLetterDesignationsSince |
P5539
|
FINISHED |
| Object | 1967 |
—
|
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: 1967 | Statement: [BMT lines, usesLetterDesignationsSince, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLetterDesignationsSince Context triple: [BMT lines, usesLetterDesignationsSince, 1967]
-
A.
hasLetterDesignation
chosen
Indicates that an entity is assigned or associated with a specific letter-based designation or code.
-
B.
letterOrNumberDesignation
Indicates that something is identified or labeled using a specific letter, number, or combination of both.
-
C.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
-
D.
usesLatinAlphabetSince
Indicates that an entity has employed the Latin alphabet as its writing system starting from a specific point in time and continuing thereafter.
-
E.
capitalAfter1954
Indicates that an entity became the capital of a place after the year 1954.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb77cc351481908d7dcd6d3d15d59f |
completed | March 31, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.