Triple
T2733262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piping Shrike |
E60366
|
entity |
| Predicate | emblematicRole |
P16921
|
FINISHED |
| Object | state bird symbol of South Australia |
—
|
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: state bird symbol of South Australia | Statement: [Piping Shrike, emblematicRole, state bird symbol of South Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblematicRole Context triple: [Piping Shrike, emblematicRole, state bird symbol of South Australia]
-
A.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
B.
emblemName
chosen
Indicates that a specified name is the official or recognized title of an emblem.
-
C.
ceremonialRole
Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
-
D.
commemoratesRoleAs
Indicates that something serves to honor or recognize a specific role or position held by an entity.
-
E.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaf175808190acbbb3873c7c3f67 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.