Triple
T8224267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMT lines |
E192138
|
entity |
| Predicate | includesFormerService |
P3388
|
FINISHED |
| Object | BMT 1 (Brighton Local) historical designation |
—
|
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: BMT 1 (Brighton Local) historical designation | Statement: [BMT lines, includesFormerService, BMT 1 (Brighton Local) historical designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFormerService Context triple: [BMT lines, includesFormerService, BMT 1 (Brighton Local) historical designation]
-
A.
hasFormerService
chosen
Indicates that an entity previously provided a service to another entity but no longer does so.
-
B.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
-
C.
servedInRole
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
-
D.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
E.
alsoServeIn
Indicates that an entity serves in an additional role, position, or capacity alongside its primary one.
- 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.