Triple
T25176907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judicial Greffier |
E630472
|
entity |
| Predicate | officeHoldsSealOf |
P11470
|
FINISHED |
| Object | Royal Court of Jersey |
—
|
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: Royal Court of Jersey | Statement: [Judicial Greffier, officeHoldsSealOf, Royal Court of Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHoldsSealOf Context triple: [Judicial Greffier, officeHoldsSealOf, Royal Court of Jersey]
-
A.
officeHeldOf
Indicates that a specific office or position is (or was) held by a particular person or entity.
-
B.
departmentSeal
chosen
Indicates that one entity serves as the official seal or emblem representing a particular department.
-
C.
officeHeldUnder
Indicates that one entity holds or has held an official position, role, or office under the authority, jurisdiction, or administration of another entity.
-
D.
isSealOf
Indicates that one entity serves as the official seal, emblem, or stamp that authenticates, endorses, or formally represents another entity.
-
E.
officeHeldTogetherWith
Indicates that two or more individuals simultaneously held the same office or position during an overlapping period.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 21, 2026, 12:34 p.m.