Triple
T28188169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese honors system |
E716232
|
entity |
| Predicate | highestDecoration |
P8755
|
FINISHED |
| Object | Order of the Chrysanthemum |
—
|
NE NERFINISHED |
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: Order of the Chrysanthemum | Statement: [Japanese honors system, highestDecoration, Order of the Chrysanthemum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestDecoration Context triple: [Japanese honors system, highestDecoration, Order of the Chrysanthemum]
-
A.
highestDecorationOf
chosen
Indicates that one decoration or honor is the most prestigious or highest-ranking award received by a given entity.
-
B.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
C.
highestPart
Indicates that one entity is the topmost or uppermost portion of another entity.
-
D.
topDecorationWeight
Indicates the weight or mass of the decorative element located at the top of an object or structure.
-
E.
notableDecoration
Indicates that an entity has received a particular honor, award, or decoration that is considered especially significant or distinguished.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 10:24 p.m.