Triple
T26957655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B (IND Concourse Line) |
E678951
|
entity |
| Predicate | introducedAsServiceLetter |
P152832
|
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: [B (IND Concourse Line), introducedAsServiceLetter, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsServiceLetter Context triple: [B (IND Concourse Line), introducedAsServiceLetter, 1967]
-
A.
usesLetteredServices
Indicates that an entity makes use of services that are identified or categorized by letter-based designations.
-
B.
introducedForServiceWith
Indicates that one entity was presented or brought to the attention of another entity specifically for the purpose of providing a service.
-
C.
introducedForServiceOn
chosen
Indicates that something was first put into official use or operation for a particular service on a specified date or occasion.
-
D.
introducedToService
Indicates that one entity has presented or brought another entity into contact with a particular service for the first time.
-
E.
takenIntoServiceAs
Indicates that one entity has been formally accepted, enrolled, or commissioned to perform service or duty for another entity.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 6:28 a.m.