Triple
T30989303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Prince |
E789621
|
entity |
| Predicate | mayExercisePowerAs |
P138745
|
FINISHED |
| Object | regent |
—
|
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: regent | Statement: [Crown Prince, mayExercisePowerAs, regent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayExercisePowerAs Context triple: [Crown Prince, mayExercisePowerAs, regent]
-
A.
mayExerciseReservePowers
Indicates that an entity is permitted to invoke or use special reserve powers under certain conditions.
-
B.
canExercisePowersOf
chosen
Indicates that one entity is authorized or able to perform, on behalf of another entity, the powers, rights, or authorities that the other entity possesses.
-
C.
exercisedPowerWith
Indicates that one entity actively used or exerted power in conjunction with another entity, implying a shared or coordinated exercise of authority or influence.
-
D.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
E.
typeOfPowerExercised
Indicates the specific kind or nature of power or authority that is being exercised in a given relationship or context.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:56 p.m.