Triple
T25500980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursus arctos |
E639107
|
entity |
| Predicate | usedAsNationalAnimalOf |
P319
|
FINISHED |
| Object | Russia |
—
|
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: Russia | Statement: [Ursus arctos, usedAsNationalAnimalOf, Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsNationalAnimalOf Context triple: [Ursus arctos, usedAsNationalAnimalOf, Russia]
-
A.
hasNationalSymbol
Indicates that an entity possesses or is associated with an officially recognized national symbol of a country or nation.
-
B.
hasNationalSymbolAssociation
Indicates a relationship where an entity is associated with, represented by, or linked to a particular national symbol.
-
C.
nationalBird
Indicates that one entity is officially designated as the national bird or avian symbol of another entity (typically a country or region).
-
D.
hasOfficialStateAnimal
chosen
Indicates that a political entity has a formally designated animal recognized as its official state symbol.
-
E.
influencedNationalSymbol
Indicates that one entity had a formative impact on the creation, design, or adoption of a national symbol associated with another 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 2:42 p.m.