Triple
T12548111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Cordon |
E300024
|
entity |
| Predicate | hasNotableRecipientGroup |
P105834
|
FINISHED |
| Object | Japanese emperors |
—
|
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: Japanese emperors | Statement: [Grand Cordon, hasNotableRecipientGroup, Japanese emperors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRecipientGroup Context triple: [Grand Cordon, hasNotableRecipientGroup, Japanese emperors]
-
A.
hasNotableRelativeGroup
Indicates that an entity is associated with a group of relatives who are notable or significant in some recognized way.
-
B.
hasRecipientRole
Indicates that a specified entity serves as the recipient or target role in a given interaction, transaction, or relationship.
-
C.
notableRecipient
Indicates that an entity has received a notable award, honor, or recognition from another entity.
-
D.
hasFirstRecipient
Indicates that an entity is the initial or primary recipient of something (such as a message, award, or transfer) in a sequence or set of recipients.
-
E.
notableRecipientType
Indicates that an entity is notably recognized as a recipient of something (such as an award, honor, or distinction) of a specified type.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95f5148948190946a575d812b329d |
completed | April 10, 2026, 8:36 p.m. |
Created at: April 8, 2026, 9:58 p.m.