Triple
T646042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston and Maine Railroad |
E11243
|
entity |
| Predicate | endedOperationsAsIndependentCompany |
P17662
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [Boston and Maine Railroad, endedOperationsAsIndependentCompany, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedOperationsAsIndependentCompany Context triple: [Boston and Maine Railroad, endedOperationsAsIndependentCompany, 1983]
-
A.
underlyingCommencedOperations
Indicates that the referenced underlying entity has begun its operational activities or business functions.
-
B.
finalOperations
Indicates that an entity is involved in the last or concluding set of actions or processes within a sequence or workflow.
-
C.
associatedOperation
Indicates that one entity is linked to or involved with a particular operation, process, or activity.
-
D.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
E.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
- F. None of above. chosen
Provenance (4 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f1b24b08190897d8aedb877bd83 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0c0dcc8190849211d45489a5a7 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49df0de3c81909721eb391ec94031 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.