Triple
T520595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chancellor of the Order of the Garter |
E10805
|
entity |
| Predicate | isOfficeWithin |
P11900
|
FINISHED |
| Object | English orders of chivalry |
—
|
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: English orders of chivalry | Statement: [Chancellor of the Order of the Garter, isOfficeWithin, English orders of chivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficeWithin Context triple: [Chancellor of the Order of the Garter, isOfficeWithin, English orders of chivalry]
-
A.
includedOffice
chosen
Indicates that one office is contained within, or forms part of, another office or organizational unit.
-
B.
worksWithOffice
Indicates that an entity collaborates or is professionally associated with a particular office or office-based organization.
-
C.
hasOfficeType
Indicates that an entity’s office is classified as a specific type or category of office.
-
D.
usedByOffice
Indicates that something is utilized, operated, or employed by an office or office-related entity.
-
E.
establishedOffice
Indicates that an entity created or set up an official office or place of operation.
- 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.