Triple
T4062907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TPWS |
E86256
|
entity |
| Predicate | operatorDomain |
P41907
|
FINISHED |
| Object | mainline railways in Great Britain |
—
|
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: mainline railways in Great Britain | Statement: [TPWS, operatorDomain, mainline railways in Great Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorDomain Context triple: [TPWS, operatorDomain, mainline railways in Great Britain]
-
A.
operateIn
chosen
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
B.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
C.
otherOperator
Indicates a relationship where one operator is distinguished from, or serves as an alternative to, another operator within the same context or system.
-
D.
operatorPlanned
Indicates that an operator has scheduled or arranged a specific action, process, or operation to occur.
-
E.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.