Triple
T9458404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Administrative Court |
E228076
|
entity |
| Predicate | alsoSitsWith |
P89057
|
FINISHED |
| Object | deputy High Court 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: deputy High Court judges | Statement: [Administrative Court, alsoSitsWith, deputy High Court judges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoSitsWith Context triple: [Administrative Court, alsoSitsWith, deputy High Court judges]
-
A.
alsoMetAt
Indicates that the same entities met together at an additional, distinct place or event beyond a previously mentioned meeting location.
-
B.
maySitWith
Indicates that one entity is permitted or allowed to sit together with another entity.
-
C.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
D.
jointSittingProvidedBy
Indicates that a joint sitting (e.g., a combined session or meeting) is organized, arranged, or supplied by a particular provider or authority.
-
E.
hasSisterChair
Indicates that one chair is related to another chair as its sister, typically implying a closely associated or counterpart chair within the same set or context.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f924f3081909dd937cbe6802881 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69ccbf9b080c819098934a18cf2bac5d |
completed | April 1, 2026, 6:47 a.m. |
Created at: March 30, 2026, 7:52 p.m.