Triple
T5076787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humbert I, Count of Savoy |
E114415
|
entity |
| Predicate | sourceOfPower |
P61281
|
FINISHED |
| Object | imperial grants from the Holy Roman Emperor |
—
|
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: imperial grants from the Holy Roman Emperor | Statement: [Humbert I, Count of Savoy, sourceOfPower, imperial grants from the Holy Roman Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceOfPower Context triple: [Humbert I, Count of Savoy, sourceOfPower, imperial grants from the Holy Roman Emperor]
-
A.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
-
B.
methodOfGainingPower
Indicates the way or process through which an entity acquires or increases power.
-
C.
createsPower
Indicates that one entity is the source or generator of power, energy, or influence for another entity or system.
-
D.
typeOfPowerGranted
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
E.
strengthSource
Indicates that one entity serves as the origin or provider of strength, power, or resilience for another entity.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d3b0088190a658864cb120eef4 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd73d90b608190bd6c2407e84e2b64 |
completed | March 20, 2026, 4:20 p.m. |
Created at: March 20, 2026, 1:39 p.m.