Triple
T17927795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA Fairmount Line |
E448241
|
entity |
| Predicate | becamePermanentService |
P79041
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [MBTA Fairmount Line, becamePermanentService, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becamePermanentService Context triple: [MBTA Fairmount Line, becamePermanentService, 1980s]
-
A.
permanentServiceBegan
chosen
Indicates that an entity’s ongoing or long-term service or role officially started at a specific point in time.
-
B.
madePermanentBy
Indicates that one entity causes another entity, condition, or status to become lasting, fixed, or indefinitely maintained.
-
C.
introducedToService
Indicates that one entity has presented or brought another entity into contact with a particular service for the first time.
-
D.
definesAsPermanentAgency
Indicates that one entity formally establishes another entity as a permanent agency or enduring representative body, rather than a temporary or ad hoc arrangement.
-
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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a5505af88190aa7a5cfee0baa3a4 |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:20 a.m.