Triple
T31355955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanak flag |
E799730
|
entity |
| Predicate | symbolismOfFlècheFaîtière |
P99574
|
FINISHED |
| Object | Kanak chiefdom |
—
|
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: Kanak chiefdom | Statement: [Kanak flag, symbolismOfFlècheFaîtière, Kanak chiefdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolismOfFlècheFaîtière Context triple: [Kanak flag, symbolismOfFlècheFaîtière, Kanak chiefdom]
-
A.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
-
B.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
C.
symbolismFocus
Indicates that the primary emphasis of a work, element, or representation is on its symbolic meaning rather than its literal or functional aspects.
-
D.
fieldSymbolism
Indicates the symbolic meaning or thematic associations that a field (as a setting, area, or domain) conveys within a given context.
-
E.
flagDesignSymbolism
chosen
Indicates the symbolic meanings or concepts represented by elements in a flag’s design.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 9:17 p.m.