Triple
T5266553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Ireland |
E118950
|
entity |
| Predicate | seatAllocation |
P51117
|
FINISHED |
| Object | 20 members from Northern Ireland |
—
|
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 members from Northern Ireland | Statement: [Council of Ireland, seatAllocation, 20 members from Northern Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatAllocation Context triple: [Council of Ireland, seatAllocation, 20 members from Northern Ireland]
-
A.
seatNumber
Indicates the specific numbered position assigned to a seat within a defined seating arrangement or venue.
-
B.
seatNotationSystem
Indicates the system or convention used to label, number, or otherwise denote seats within a venue or vehicle.
-
C.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
-
D.
seatsAreAllocatedTo
chosen
Indicates that specific seats are assigned or designated to particular entities (such as people, groups, or bookings).
-
E.
individualSeats
Indicates that an entity provides or consists of separate, single-person seating positions rather than shared or bench-style seating.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.