Triple
T4448233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor-General |
E96341
|
entity |
| Predicate | exercisesPowerOnBehalfOf |
P6039
|
FINISHED |
| Object | monarch |
—
|
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: monarch | Statement: [Governor-General, exercisesPowerOnBehalfOf, monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exercisesPowerOnBehalfOf Context triple: [Governor-General, exercisesPowerOnBehalfOf, monarch]
-
A.
actsOnBehalfOf
Indicates that one entity performs actions or makes decisions as a representative or proxy for another entity.
-
B.
exerciseOfPower
Indicates the exertion or application of authority, control, or influence by one entity over another or within a given context.
-
C.
builtOnBehalfOf
Indicates that something was constructed or created by one party acting as a representative or agent for another party.
-
D.
exercisesPowerInNameOf
chosen
Indicates that one entity wields authority or influence on behalf of, and under the authorization or representation of, another entity.
-
E.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d45b748190b09b7067fc6279b0 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.