Triple
T3917069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMS Black Five |
E88866
|
entity |
| Predicate | whyNickname |
P7596
|
FINISHED |
| Object | black livery and power classification 5MT |
—
|
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: black livery and power classification 5MT | Statement: [LMS Black Five, whyNickname, black livery and power classification 5MT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: whyNickname Context triple: [LMS Black Five, whyNickname, black livery and power classification 5MT]
-
A.
reasonForNickname
chosen
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
B.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
-
C.
nickNameMeaning
Indicates that a nickname is associated with a particular meaning, interpretation, or significance.
-
D.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for another entity.
-
E.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.