Triple
T9282042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assembly of Kosovo |
E223091
|
entity |
| Predicate | reservedSeats |
P9399
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Assembly of Kosovo, reservedSeats, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservedSeats Context triple: [Assembly of Kosovo, reservedSeats, 20]
-
A.
hasReservedSeats
chosen
Indicates that specific seats have been set aside or allocated in advance for a particular entity or purpose.
-
B.
individualSeats
Indicates that an entity provides or consists of separate, single-person seating positions rather than shared or bench-style seating.
-
C.
seatIs
Indicates that one entity functions as the seat or seating position of another entity.
-
D.
seatSince
Indicates that an entity has held a particular seat, position, or place continuously since a specified point in time.
-
E.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081c2b048190aa6930de3bf2f87f |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.