Triple
T25569116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourbon royal white flag standards |
E640923
|
entity |
| Predicate | emblazonedWith |
P23430
|
FINISHED |
| Object | royal arms of France |
—
|
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: royal arms of France | Statement: [Bourbon royal white flag standards, emblazonedWith, royal arms of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblazonedWith Context triple: [Bourbon royal white flag standards, emblazonedWith, royal arms of France]
-
A.
adornedWith
chosen
Indicates that one entity is decorated, embellished, or ornamented by another entity.
-
B.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
C.
emblematicFor
Indicates that something serves as a representative symbol or characteristic example of something else.
-
D.
armorMarkings
Indicates that one entity bears specific markings, patterns, or insignia on its armor in relation to another entity or context.
-
E.
protectiveEmblemName
Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8fedd38819096b4cb0016019b7d |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:56 p.m.