Triple
T4027144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadian Air Force ensign |
E83617
|
entity |
| Predicate | roundelRepresents |
P9820
|
FINISHED |
| Object | Royal Canadian Air Force identity |
—
|
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: Royal Canadian Air Force identity | Statement: [Royal Canadian Air Force ensign, roundelRepresents, Royal Canadian Air Force identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundelRepresents Context triple: [Royal Canadian Air Force ensign, roundelRepresents, Royal Canadian Air Force identity]
-
A.
roundel
chosen
Indicates that one entity bears, displays, or is marked with a circular emblem or symbol representing another entity.
-
B.
round
Indicates that an entity has a circular or approximately circular shape or form.
-
C.
ringRadius
Indicates the size of a ring by specifying the distance from its center to its outer edge.
-
D.
ringName
Indicates that a ring is identified or referred to by a specific name.
-
E.
ringPlane
Indicates that one entity lies within or corresponds to the geometric plane defined by a ring structure associated with another entity.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaed37e48190844032e7e77163e0 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.