Triple
T31002148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emblem of Kosovo |
E789967
|
entity |
| Predicate | governmentApprovedBy |
P807
|
FINISHED |
| Object | Assembly of Kosovo |
—
|
NE NERFINISHED |
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: Assembly of Kosovo | Statement: [Emblem of Kosovo, governmentApprovedBy, Assembly of Kosovo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentApprovedBy Context triple: [Emblem of Kosovo, governmentApprovedBy, Assembly of Kosovo]
-
A.
isApprovedFor
Indicates that one entity has been officially authorized, accepted, or permitted for use, access, or association with another entity.
-
B.
approvedBy
chosen
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
C.
stateApproval
Indicates that an action, decision, or entity has been formally reviewed and authorized by a governmental or state-level authority.
-
D.
statuteApprovedBy
Indicates that a statute has received formal approval or authorization from a specified person, body, or authority.
-
E.
recognizedGovernment
Indicates that one entity formally acknowledges another entity as the legitimate governing authority of a state or territory.
- 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_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: April 29, 2026, 8:57 p.m.