Triple
T31002123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emblem of Kosovo |
E789967
|
entity |
| Predicate | positionOfMap |
P36479
|
FINISHED |
| Object | center of shield |
—
|
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: center of shield | Statement: [Emblem of Kosovo, positionOfMap, center of shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfMap Context triple: [Emblem of Kosovo, positionOfMap, center of shield]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
mapLocation
chosen
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
C.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
-
D.
locationPosed
Indicates that an entity is positioned or situated at a specific location.
-
E.
positionObtainedBy
Indicates that a particular position or role is acquired, achieved, or secured through a specified action, process, or agent.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 29, 2026, 8:57 p.m.