Triple
T7478155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentine flag |
E176681
|
entity |
| Predicate | emblemInstanceOf |
P29556
|
FINISHED |
| Object | national emblem of Argentina |
—
|
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 emblem of Argentina | Statement: [Argentine flag, emblemInstanceOf, national emblem of Argentina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemInstanceOf Context triple: [Argentine flag, emblemInstanceOf, national emblem of Argentina]
-
A.
emblematicFor
Indicates that something serves as a representative symbol or characteristic example of something else.
-
B.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
C.
emblemStatus
Indicates the current state or condition of an emblem, such as whether it is active, valid, displayed, or in use.
-
D.
emblemUsedBy
chosen
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
E.
emblemFeatures
Indicates that an emblem includes or displays specific visual elements or characteristics.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4f0088c8190880770ac31e5b7a7 |
completed | March 27, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.