Triple
T18667664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown officer |
E456381
|
entity |
| Predicate | performsDutiesFor |
P58267
|
FINISHED |
| Object | the sovereign |
—
|
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: the sovereign | Statement: [Crown officer, performsDutiesFor, the sovereign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsDutiesFor Context triple: [Crown officer, performsDutiesFor, the sovereign]
-
A.
performsDuty
chosen
Indicates that one entity carries out or fulfills a responsibility, task, or obligation on behalf of or in relation to another entity.
-
B.
hasDutiesUnder
Indicates that one party is obligated to perform specific responsibilities or fulfill obligations as defined by another party, agreement, or authority.
-
C.
hasPrimaryDuty
Indicates that one entity holds the main or most important responsibility or obligation toward another entity or within a specified context.
-
D.
responsibleFor
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
E.
assumesDutiesOf
Indicates that one entity takes over and begins performing the responsibilities or role previously held by another entity.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556af6bac8190a6615d44604d784d |
completed | April 19, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.