Triple
T520615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chancellor of the Order of the Garter |
E10805
|
entity |
| Predicate | isOfficeHeldBy |
P4012
|
FINISHED |
| Object | a senior peer |
—
|
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: a senior peer | Statement: [Chancellor of the Order of the Garter, isOfficeHeldBy, a senior peer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficeHeldBy Context triple: [Chancellor of the Order of the Garter, isOfficeHeldBy, a senior peer]
-
A.
officeHolderOf
Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
-
B.
officeHolderMayBe
Indicates that a specified person is permitted or eligible to hold a particular office or position.
-
C.
isElectoralOffice
Indicates that the referenced position or role is an official public office filled through an electoral process.
-
D.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
-
E.
isOfficerOf
chosen
Indicates that one entity holds an official position, role, or office within another entity (such as an organization, group, or institution).
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1a1817c8190a6cc8f423071d3ad |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f016ba5c81909825b04e7525b4ab |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.