Triple
T17778149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NE-92 trains |
E443825
|
entity |
| Predicate | operationStatus |
P5870
|
FINISHED |
| Object | in service (as electric multiple units on Line 2) |
—
|
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: in service (as electric multiple units on Line 2) | Statement: [NE-92 trains, operationStatus, in service (as electric multiple units on Line 2)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationStatus Context triple: [NE-92 trains, operationStatus, in service (as electric multiple units on Line 2)]
-
A.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
B.
operatingStatus
chosen
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
C.
automationStatus
Indicates whether a process, task, or system is being performed automatically or requires manual intervention.
-
D.
runtimeStatus
Indicates the current operational state or condition of an entity while it is running or executing.
-
E.
programStatus
Indicates the current state or condition of a program within its lifecycle (e.g., planned, active, paused, completed, or terminated).
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4871e06a481909cf6d59e49dc21c5 |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.