Triple
T27726315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wappen Berlins |
E699106
|
entity |
| Predicate | positionOnShield |
P185195
|
FINISHED |
| Object | bear 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: bear rampant | Statement: [Wappen Berlins, positionOnShield, bear rampant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnShield Context triple: [Wappen Berlins, positionOnShield, bear rampant]
-
A.
shieldPosition
Indicates the relative location or orientation of a shield with respect to the entity or context it is protecting.
-
B.
positionOnWeapons
Indicates a stance, policy, or viewpoint that an entity holds regarding weapons or weapon-related issues.
-
C.
positionInWall
Indicates that one entity occupies a specific location or placement within a wall.
-
D.
positionOnSecurity
Indicates the stance, opinion, or policy an entity holds regarding security-related issues or measures.
-
E.
hasShieldBearer
Indicates that one entity serves as the shield-bearing protector or defensive attendant for another entity.
- F. None of above. chosen
Provenance (4 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: April 27, 2026, 3:09 p.m.