Triple
T25568471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | law lord |
E640903
|
entity |
| Predicate | couldSitIn |
P36258
|
FINISHED |
| Object | Judicial Committee of the Privy Council |
—
|
NE NERFINISHED |
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: Judicial Committee of the Privy Council | Statement: [law lord, couldSitIn, Judicial Committee of the Privy Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldSitIn Context triple: [law lord, couldSitIn, Judicial Committee of the Privy Council]
-
A.
canSitIn
chosen
Indicates that one entity is able or permitted to sit inside or occupy the seating space of another entity.
-
B.
maySit
Indicates that one entity is permitted or allowed to sit on or in another entity.
-
C.
canSitWithout
Indicates that one entity is able to sit without the presence, support, or assistance of another entity.
-
D.
maySitWith
Indicates that one entity is permitted or allowed to sit together with another entity.
-
E.
cannotSit
Indicates that an entity is unable or not allowed to sit on, in, or at 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8fe0abc8190862167a5d282e107 |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:50 p.m.