Triple
T35990902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Greenland |
E1040841
|
entity |
| Predicate | bearAttitude |
P105887
|
FINISHED |
| Object | rampant |
—
|
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: rampant | Statement: [Coat of arms of Greenland, bearAttitude, rampant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearAttitude Context triple: [Coat of arms of Greenland, bearAttitude, rampant]
-
A.
bearerStance
chosen
Indicates the attitude, position, or viewpoint that the bearer holds toward a referenced subject or issue.
-
B.
bearer
Indicates that one entity carries, holds, or possesses another entity, often as the current holder of a right, document, or object.
-
C.
bracing
Indicates that one entity is supporting, reinforcing, or steadying another to prevent movement, collapse, or strain.
-
D.
chargeAttitude
Indicates a person's evaluative stance or feelings toward a financial or legal charge (such as a fee, cost, or accusation).
-
E.
boreTheBruntOf
Indicates that one entity received or endured the main force, impact, or negative consequences of an action or event caused by 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.