Triple
T2347267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the Rising Sun |
E45158
|
entity |
| Predicate | notableRecipientCategory |
P14626
|
FINISHED |
| Object | politicians |
—
|
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: politicians | Statement: [Order of the Rising Sun, notableRecipientCategory, politicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRecipientCategory Context triple: [Order of the Rising Sun, notableRecipientCategory, politicians]
-
A.
notableRecipientType
Indicates that an entity is notably recognized as a recipient of something (such as an award, honor, or distinction) of a specified type.
-
B.
notableFieldOfRecipients
chosen
Indicates that the recipients are notable or recognized specifically in a particular field or area of expertise.
-
C.
notableRecipient
Indicates that an entity has received a notable award, honor, or recognition from another entity.
-
D.
notableCategory
Indicates that an entity is recognized as notable or significant within a particular category or classification.
-
E.
holderNotableFor
Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.