Triple
T16560889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMS Royal Scot Class |
E402333
|
entity |
| Predicate | powerClassificationBR |
P14438
|
FINISHED |
| Object | 6P |
—
|
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: 6P | Statement: [LMS Royal Scot Class, powerClassificationBR, 6P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerClassificationBR Context triple: [LMS Royal Scot Class, powerClassificationBR, 6P]
-
A.
powerClassification
chosen
Indicates how an entity’s power, strength, or influence is categorized or ranked within a defined system.
-
B.
typeOfPolity
Indicates that one entity is a political unit and the other specifies the kind or classification of that polity (e.g., empire, kingdom, republic).
-
C.
politicalEntityTypeRuled
Indicates the type or category of political entity over which a ruler or governing authority exercises control or sovereignty.
-
D.
governsInPoliticalSystem
Indicates that one entity exercises authoritative control or rule over another entity within a specified political system or structure.
-
E.
countryGoverningBody
Indicates that a particular governing body holds official authority over and administers a specific country.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576d88288190b33543bea4706a36 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.