Triple
T34904695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of British Columbia |
E1006687
|
entity |
| Predicate | usesAspect |
P182886
|
FINISHED |
| Object | defaced Blue Ensign tradition |
—
|
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: defaced Blue Ensign tradition | Statement: [flag of British Columbia, usesAspect, defaced Blue Ensign tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAspect Context triple: [flag of British Columbia, usesAspect, defaced Blue Ensign tradition]
-
A.
onAspect
Indicates that one entity is positioned on a particular side, surface, or facet of another entity.
-
B.
coversAspect
Indicates that one entity addresses, includes, or deals with a particular aspect or facet of another entity or topic.
-
C.
supportsAspect
Indicates that one entity provides backing, justification, or reinforcement for a particular aspect, feature, or component of another entity.
-
D.
refersToAspect
Indicates that one entity specifically references or points to a particular aspect, feature, or component of another entity.
-
E.
basedOnAspect
Indicates that one entity is derived, determined, or defined according to a particular aspect, feature, or dimension of another entity.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4 p.m.