Triple
T1953107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Appeal of England and Wales |
E42202
|
entity |
| Predicate | canSitAs |
P15391
|
FINISHED |
| Object | full court |
—
|
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: full court | Statement: [Court of Appeal of England and Wales, canSitAs, full court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSitAs Context triple: [Court of Appeal of England and Wales, canSitAs, full court]
-
A.
maySitByRight
Indicates that an entity has the right or permission to sit next to another entity.
-
B.
canChair
Indicates that an entity has the authority or capability to preside over, lead, or chair a meeting, committee, or similar group.
-
C.
hasSeatAt
chosen
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
D.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
-
E.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3501d108190bc5cb23f53db4411 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.