Triple
T23764121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 43 High Speed Train power cars |
E587329
|
entity |
| Predicate | recordSetOn |
P92054
|
FINISHED |
| Object | 1987-11-01 |
—
|
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: 1987-11-01 | Statement: [British Rail Class 43 High Speed Train power cars, recordSetOn, 1987-11-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordSetOn Context triple: [British Rail Class 43 High Speed Train power cars, recordSetOn, 1987-11-01]
-
A.
recordSetAgainst
Indicates that a performance, statistic, or benchmark was achieved in opposition to or during a specific event, opponent, or condition.
-
B.
setRecordFor
chosen
Indicates establishing or updating a specific record associated with an entity or context.
-
C.
recordSetInSeason
Indicates that a particular record or achievement was set during a specified sports season.
-
D.
setsOn
Indicates that one entity places or arranges another entity onto a specified surface, container, or context.
-
E.
recordsWith
Indicates that one entity keeps or maintains documented information about another entity or event.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb4e9248190b64b063637b66702 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.