Triple
T16470613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMS Coronation Class |
E400048
|
entity |
| Predicate | recordClaim |
P122910
|
FINISHED |
| Object | high-speed runs exceeding 110 mph |
—
|
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: high-speed runs exceeding 110 mph | Statement: [LMS Coronation Class, recordClaim, high-speed runs exceeding 110 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordClaim Context triple: [LMS Coronation Class, recordClaim, high-speed runs exceeding 110 mph]
-
A.
claimProcess
Indicates the process by which a claim (such as an insurance or service claim) is received, evaluated, and resolved between involved parties.
-
B.
recognizedClaimOf
Indicates that one entity formally acknowledges the validity or legitimacy of a claim made by another entity.
-
C.
resultOfClaim
Indicates that something occurs as a consequence or outcome of a specific claim or assertion.
-
D.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
E.
challengesClaim
Indicates that one entity disputes, questions, or opposes the validity or correctness of another entity’s claim.
- F. None of above. chosen
Provenance (4 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dd0d2fc81909b68b5afb00f192f |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:11 a.m.