Triple
T21411992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonwealth of Nations vice-regal offices |
E528193
|
entity |
| Predicate | oftenHoldsTitle |
P143865
|
FINISHED |
| Object | Her Excellency |
—
|
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: Her Excellency | Statement: [Commonwealth of Nations vice-regal offices, oftenHoldsTitle, Her Excellency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenHoldsTitle Context triple: [Commonwealth of Nations vice-regal offices, oftenHoldsTitle, Her Excellency]
-
A.
mayHoldTitleOf
Indicates that an entity is permitted or eligible to possess or bear a particular title.
-
B.
heldTitleAlongWith
Indicates that two or more entities simultaneously held the same title or position during an overlapping period.
-
C.
titleHeldAs
Indicates that an entity holds or possesses a specific title in a particular capacity or role.
-
D.
heldTitleUnder
Indicates that one entity possessed or occupied a particular title, rank, or office under the authority, jurisdiction, or auspices of another entity.
-
E.
titleHeldTo
Indicates that one entity holds or possesses a specific title in relation to another entity 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee62d01634819089dd64fe7bc5ccbd |
completed | April 26, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:43 p.m.