Triple
T2786759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the Chrysanthemum |
E61827
|
entity |
| Predicate | collarFeature |
P43568
|
FINISHED |
| Object | chrysanthemum flowers |
—
|
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: chrysanthemum flowers | Statement: [Order of the Chrysanthemum, collarFeature, chrysanthemum flowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collarFeature Context triple: [Order of the Chrysanthemum, collarFeature, chrysanthemum flowers]
-
A.
supporterCollar
Indicates that one entity serves as a collar-like structural element that supports or stabilizes another entity.
-
B.
dressFeature
Indicates that a dress possesses or is characterized by a particular feature, attribute, or design element.
-
C.
brandAttribute
Indicates that a specific attribute or characteristic is associated with, or describes, a particular brand.
-
D.
wardrobeFeature
Indicates that a wardrobe possesses or includes a specific feature, attribute, or functional element.
-
E.
accessory
Indicates that one entity serves as a supplementary or supporting item to another, often enhancing its function, use, or appearance.
- 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdee94c2081908e5075e87e70780a |
completed | March 7, 2026, 8:16 a.m. |
Created at: March 6, 2026, 9:57 p.m.