Triple
T25863939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNER Class A4 |
E651559
|
entity |
| Predicate | operatorAfterGrouping |
P153661
|
FINISHED |
| Object | British Railways |
—
|
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 Railways | Statement: [LNER Class A4, operatorAfterGrouping, British Railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAfterGrouping Context triple: [LNER Class A4, operatorAfterGrouping, British Railways]
-
A.
orderOfPrecedenceGroup
Indicates the hierarchical ranking or priority grouping of entities relative to one another.
-
B.
hasPostgroupOperator
Indicates that one entity is associated with an operator that is applied after a primary operation or grouping has been performed on another entity.
-
C.
operatorAfterConsolidation
chosen
Indicates that one operator entity succeeds or replaces another operator entity after a consolidation event (such as a merger or acquisition).
-
D.
operatorAfterCapture
Indicates that one operator or action is applied immediately after a capture event has occurred.
-
E.
laterAddedGrouping
Indicates that one grouping was created or introduced after another, establishing a temporal ordering between the groupings.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 22, 2026, 8:06 a.m.