Triple
T29384664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Niger |
E745218
|
entity |
| Predicate | flagTypeFlankingShield |
P73103
|
FINISHED |
| Object | national flag of Niger |
—
|
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: national flag of Niger | Statement: [coat of arms of Niger, flagTypeFlankingShield, national flag of Niger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagTypeFlankingShield Context triple: [coat of arms of Niger, flagTypeFlankingShield, national flag of Niger]
-
A.
flagOrInsignia
chosen
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
B.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
C.
flagElement
Indicates that one entity serves as a flag or marker element associated with another entity, typically used to signal a condition, state, or special handling.
-
D.
flagBearer
Indicates that one entity serves as the carrier or holder of a flag on behalf of another entity, group, or cause.
-
E.
flagshipType
Indicates that one entity is the primary or most important representative (flagship) of a particular type, category, or group defined by the other 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d0c45c8190ac5b67a0e89e8aae |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:37 p.m.