Triple
T12950461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Nunatsiavut |
E309877
|
entity |
| Predicate | writingOnFlag |
P64836
|
FINISHED |
| Object | Nunatsiavut in Inuttitut syllabics |
—
|
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: Nunatsiavut in Inuttitut syllabics | Statement: [Flag of Nunatsiavut, writingOnFlag, Nunatsiavut in Inuttitut syllabics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingOnFlag Context triple: [Flag of Nunatsiavut, writingOnFlag, Nunatsiavut in Inuttitut syllabics]
-
A.
isOnFlagOf
chosen
Indicates that something (typically a symbol, image, or design element) appears on or is depicted on a flag.
-
B.
flagDesigner
Indicates that one entity is the person or group responsible for designing the flag associated with another entity.
-
C.
flagFlown
Indicates that a particular flag is being displayed or flown at a specific location or by a specific entity.
-
D.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
E.
writingForm
Indicates the specific script, notation, or written representation used to express a piece of language or content.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.