Triple
T350562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Crown |
E7432
|
entity |
| Predicate | exercisesPower |
P6502
|
FINISHED |
| Object | executive authority |
—
|
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: executive authority | Statement: [British Crown, exercisesPower, executive authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exercisesPower Context triple: [British Crown, exercisesPower, executive authority]
-
A.
exercisesPowerInNameOf
Indicates that one entity wields authority or influence on behalf of, and under the authorization or representation of, another entity.
-
B.
freeExerciseTest
Indicates a legal assessment of whether a law or government action improperly burdens or restricts an individual’s or group’s free exercise of religion.
-
C.
pumpingPower
Indicates the rate at which energy is supplied or transferred by a pump to move a fluid or medium.
-
D.
exercisedPowerOver
chosen
Indicates that one entity exerted control, influence, or authority over another entity.
-
E.
strength
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb1f028c819098fa6480b4ca5cf0 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.