Triple
T23695905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 143 |
E585443
|
entity |
| Predicate | primaryRegionsOfOperation |
P6665
|
FINISHED |
| Object | South West England |
—
|
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: South West England | Statement: [British Rail Class 143, primaryRegionsOfOperation, South West England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRegionsOfOperation Context triple: [British Rail Class 143, primaryRegionsOfOperation, South West England]
-
A.
operatedInRegion
chosen
Indicates that an entity conducted operations or activities within a specified geographic region.
-
B.
operatesToRegion
Indicates that an agent conducts operations or provides services directed toward or within a specified region.
-
C.
aircraftPrimaryOperationalRegion
Indicates the main geographic area or region in which an aircraft is primarily operated or intended to operate.
-
D.
primaryLongHaulRegion
Indicates the main long-distance geographic region in which an entity primarily operates or is associated for long-haul activities.
-
E.
operatesInCountries
Indicates that an entity conducts its activities or business within the specified countries.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c65ab88190be59a8fb731cf030 |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.