Triple
T30029425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exposition Corridor |
E762970
|
entity |
| Predicate | hasFormerRailOperator |
P84160
|
FINISHED |
| Object | Pacific Electric Railway |
—
|
NE NERFINISHED |
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: Pacific Electric Railway | Statement: [Exposition Corridor, hasFormerRailOperator, Pacific Electric Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerRailOperator Context triple: [Exposition Corridor, hasFormerRailOperator, Pacific Electric Railway]
-
A.
formerRailOperator
chosen
Indicates that an entity previously operated a rail service or railway system but no longer does so.
-
B.
formerlyOperatedBy
Indicates that an entity was previously operated or managed by another entity, but is no longer under that operation.
-
C.
laterRailwayCompany
Indicates that one railway company is the successor or later incarnation of another railway company.
-
D.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
E.
hasRailOperatorNamedAfter
Indicates that a rail operator is named after the specified 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 29, 2026, 6:49 p.m.