Triple
T2057062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Winnipeg Rifles |
E45697
|
entity |
| Predicate | receivedRoyalDesignation |
P14035
|
FINISHED |
| Object | 1935 |
—
|
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: 1935 | Statement: [Royal Winnipeg Rifles, receivedRoyalDesignation, 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedRoyalDesignation Context triple: [Royal Winnipeg Rifles, receivedRoyalDesignation, 1935]
-
A.
wasCrowned
Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
-
B.
acceptedThrone
Indicates that an entity has agreed to assume and take on the role and authority associated with a throne or rulership.
-
C.
succeededToThroneAs
Indicates that one entity became the new ruler by taking over the throne in a specified role or title from another entity.
-
D.
royalDesignationYear
chosen
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
E.
crownedBy
Indicates that an entity is formally invested with a rank, title, or authority through a crowning ceremony performed by another 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9abdb088190991a620e01dc226f |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.