Triple
T37673017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 508 |
E938012
|
entity |
| Predicate | initialAreaOfOperation |
P148184
|
FINISHED |
| Object | Southern Region of British Rail |
—
|
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: Southern Region of British Rail | Statement: [British Rail Class 508, initialAreaOfOperation, Southern Region of British Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialAreaOfOperation Context triple: [British Rail Class 508, initialAreaOfOperation, Southern Region of British Rail]
-
A.
fieldOfOperation
Indicates the domain, area, or scope within which an entity operates or carries out its primary activities.
-
B.
primaryIslandOfOperation
Indicates that an entity mainly conducts its activities or operations on a specified island.
-
C.
firstAreaImplemented
chosen
Indicates the initial geographic or spatial area where something (such as a project, policy, or system) is first put into effect or deployed.
-
D.
eraOfOperation
Indicates the time period or span of years during which an entity was active or in operation.
-
E.
firstCombatOperation
Indicates that the referenced combat operation is the earliest or initial combat action undertaken by the entity in question.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:18 p.m.