Triple
T34621073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EWS |
E889003
|
entity |
| Predicate | operatedClass |
P202834
|
FINISHED |
| Object | British Rail Class 37 |
—
|
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: British Rail Class 37 | Statement: [EWS, operatedClass, British Rail Class 37]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedClass Context triple: [EWS, operatedClass, British Rail Class 37]
-
A.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
B.
operatorClass
Indicates the classification or category of an operator in terms of its type, role, or functional group within a system or domain.
-
C.
operatedWith
Indicates that an entity performed an action, function, or process using a specified tool, method, or instrument.
-
D.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
-
E.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00c3362dcc819096e49b882709fddd |
completed | May 10, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_6a00c2e5cdd88190a5f2d0f6a843cd56 |
completed | May 10, 2026, 5:39 p.m. |
| PDg | Predicate description generation | batch_6a00c3355498819088253d5e5c17267f |
completed | May 10, 2026, 5:41 p.m. |
Created at: May 1, 2026, 2:04 a.m.