Triple
T2699043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Final Appeal |
E58585
|
entity |
| Predicate | canSitWith |
P33491
|
FINISHED |
| Object | overseas non-permanent judges from other common law jurisdictions |
—
|
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: overseas non-permanent judges from other common law jurisdictions | Statement: [Court of Final Appeal, canSitWith, overseas non-permanent judges from other common law jurisdictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSitWith Context triple: [Court of Final Appeal, canSitWith, overseas non-permanent judges from other common law jurisdictions]
-
A.
canSitIn
Indicates that one entity is able or permitted to sit inside or occupy the seating space of another entity.
-
B.
maySitWith
chosen
Indicates that one entity is permitted or allowed to sit together with another entity.
-
C.
canChair
Indicates that an entity has the authority or capability to preside over, lead, or chair a meeting, committee, or similar group.
-
D.
maySitByRight
Indicates that an entity has the right or permission to sit next to another entity.
-
E.
hasSeat
Indicates that one entity possesses, provides, or includes a seat 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda339cf48190b9ae6b99137f005e |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.