Triple
T36297550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ansprand |
E893409
|
entity |
| Predicate | returnedToPowerWithSupportFrom |
P192180
|
FINISHED |
| Object | Bavarians |
—
|
NE NERFINISHED |
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: Bavarians | Statement: [Ansprand, returnedToPowerWithSupportFrom, Bavarians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToPowerWithSupportFrom Context triple: [Ansprand, returnedToPowerWithSupportFrom, Bavarians]
-
A.
attemptedReturnToPower
Indicates an effort by an entity to regain a previously held position of authority, control, or influence after having lost it.
-
B.
fellFromPowerAfter
Indicates that one entity lost its position of authority or control following the actions, rise, or influence of another entity.
-
C.
lostPowerAfter
Indicates that one entity ceased to have power or electricity following an event associated with another entity.
-
D.
fellFromPowerIn
Indicates that an entity lost its position of authority or control in a specified place or context at a particular time.
-
E.
regainedPowerAgainIn
Indicates that an entity, having previously lost power, has once more returned to a position of power or control within a specified context or location.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:09 p.m.