Triple
T1953109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Appeal of England and Wales |
E42202
|
entity |
| Predicate | maySitWith |
P33491
|
FINISHED |
| Object | 2 judges |
—
|
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: 2 judges | Statement: [Court of Appeal of England and Wales, maySitWith, 2 judges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySitWith Context triple: [Court of Appeal of England and Wales, maySitWith, 2 judges]
-
A.
maySitByRight
Indicates that an entity has the right or permission to sit next to another entity.
-
B.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
-
C.
maySitEnBanc
Indicates that a judicial body has the authority or option to convene and hear a case with all (or a large majority of) its judges sitting together as a full court.
-
D.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
-
E.
mayServeOn
Indicates that one entity is permitted or eligible to serve on another entity, such as a group, body, or committee.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69abb1ddccbc8190bf2bd8bac673c0c5 |
completed | March 7, 2026, 5:04 a.m. |
Created at: March 4, 2026, 7:36 p.m.