Triple
T964158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chair R |
E20799
|
entity |
| Predicate | seatStatus |
P18490
|
FINISHED |
| Object | individual, non-collective seat |
—
|
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: individual, non-collective seat | Statement: [Chair R, seatStatus, individual, non-collective seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatStatus Context triple: [Chair R, seatStatus, individual, non-collective seat]
-
A.
circuitSeatState
chosen
Indicates the operational or occupancy status of a seat within an electrical or electronic circuit context.
-
B.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
-
C.
seatCategory
Indicates the classification or type of a seat (e.g., by comfort level, price tier, or section) assigned to an entity.
-
D.
hasReservedSeats
Indicates that specific seats have been set aside or allocated in advance for a particular entity or purpose.
-
E.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4303e5881909d101d11f9732c75 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a2e23c8190b932fe88b02f995d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.