Triple
T15544833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of the British Antarctic Territory |
E370578
|
entity |
| Predicate | fieldSymbolizes |
P129
|
FINISHED |
| Object | Antarctic ice and snow |
—
|
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: Antarctic ice and snow | Statement: [Coat of arms of the British Antarctic Territory, fieldSymbolizes, Antarctic ice and snow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldSymbolizes Context triple: [Coat of arms of the British Antarctic Territory, fieldSymbolizes, Antarctic ice and snow]
-
A.
fieldRepresents
Indicates that one field or attribute stands for, encodes, or symbolizes another concept, value, or entity.
-
B.
symbolizedIn
Indicates that one entity serves as a symbol or representation of another entity.
-
C.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
D.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
E.
symbolElement
Indicates that one entity is a constituent element or component that makes up the other entity, which is treated as a symbol.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0443410408190a249889edcd9c599 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.