Triple
T5239815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lechmere |
E118310
|
entity |
| Predicate | hasFormerRole |
P29914
|
FINISHED |
| Object | northern terminus of the Green Line |
—
|
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: northern terminus of the Green Line | Statement: [Lechmere, hasFormerRole, northern terminus of the Green Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerRole Context triple: [Lechmere, hasFormerRole, northern terminus of the Green Line]
-
A.
mayHavePriorRole
Indicates that an entity is allowed or expected to have held a specified role at some earlier time.
-
B.
hasHistoricalRoleAs
chosen
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
-
C.
hasFormerPupilRole
Indicates that an entity previously held the role or position of a pupil or student in relation to another entity.
-
D.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
E.
hasTrainingRole
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b2a52fc8190a22631e1853c74a3 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.