Triple
T38429455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D400–D449 |
E903757
|
entity |
| Predicate | regionOfLaterOperation |
P154893
|
FINISHED |
| Object | Western 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: Western Region of British Rail | Statement: [D400–D449, regionOfLaterOperation, Western Region of British Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfLaterOperation Context triple: [D400–D449, regionOfLaterOperation, Western Region of British Rail]
-
A.
regionOfPrimaryOperation
Indicates the geographic area where an entity primarily conducts its main activities or operations.
-
B.
hasLaterStartInRegion
Indicates that one entity’s start time occurs later than another entity’s start time within a specified region or context.
-
C.
regionOfFinal
chosen
Indicates the geographic or administrative region in which something ultimately occurs, is finalized, or reaches its final state.
-
D.
regionBeforeMerger
Indicates that a region existed in its original form prior to being merged into a new or larger administrative or geographic entity.
-
E.
subsequentLaunchRegion
Indicates that one region is launched or activated after another region in a defined sequence.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a009a0e1fa481909ed881012009b268 |
completed | May 10, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_6a0092e9fcb08190a966d720684f25ec |
completed | May 10, 2026, 2:15 p.m. |
Created at: May 3, 2026, 4:31 p.m.