Triple
T7248805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MoPac |
E156541
|
entity |
| Predicate | alsoOperated |
P64555
|
FINISHED |
| Object | passenger trains |
—
|
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: passenger trains | Statement: [MoPac, alsoOperated, passenger trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoOperated Context triple: [MoPac, alsoOperated, passenger trains]
-
A.
alsoOperatedBy
chosen
Indicates that an entity is additionally operated or managed by another operator, alongside any primary or other operators.
-
B.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
C.
alsoOperatesIn
Indicates that an entity, in addition to its primary location or domain, conducts operations or activities in another specified place or context.
-
D.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
E.
formerlyOperatedBy
Indicates that an entity was previously operated or managed by another entity, but is no longer under that operation.
- 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea763f208190af1210cd8d2a05c9 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.