Triple
T26371725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emblem of the Republic of China |
E660789
|
entity |
| Predicate | nationalEmblemAdoptionYear |
P161570
|
FINISHED |
| Object | 1928 |
—
|
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: 1928 | Statement: [Emblem of the Republic of China, nationalEmblemAdoptionYear, 1928]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalEmblemAdoptionYear Context triple: [Emblem of the Republic of China, nationalEmblemAdoptionYear, 1928]
-
A.
adoptedAsOfficialSymbolInYear
chosen
Indicates that something was formally designated as an official symbol in a specific year.
-
B.
adoptedAsEmblemBy
Indicates that something has been officially chosen and used as a symbolic emblem by a particular entity or group.
-
C.
adoptedAsNationalFlagOn
Indicates that an entity was officially chosen and put into use as a country's national flag on a specific date.
-
D.
hasNationalSymbolAssociation
Indicates a relationship where an entity is associated with, represented by, or linked to a particular national symbol.
-
E.
hasNationalSymbol
Indicates that an entity possesses or is associated with an officially recognized national symbol of a country or nation.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 26, 2026, 10:58 p.m.