Triple
T18322150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexios IV Angelos |
E438908
|
entity |
| Predicate | eventLeadingToPower |
P131374
|
FINISHED |
| Object | restoration of Isaac II Angelos |
—
|
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: restoration of Isaac II Angelos | Statement: [Alexios IV Angelos, eventLeadingToPower, restoration of Isaac II Angelos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventLeadingToPower Context triple: [Alexios IV Angelos, eventLeadingToPower, restoration of Isaac II Angelos]
-
A.
lostPowerInEvent
Indicates that an entity ceased to have power or electricity as a result of a specific event.
-
B.
engagedWithPower
Indicates a relationship where an entity actively interacts, collaborates, or aligns with a source of authority, influence, or control.
-
C.
stadiumPowerOutageOccurred
Indicates that a power outage event has taken place at a stadium.
-
D.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
E.
involvesPower
Indicates that the relationship or action includes the use, exercise, transfer, or influence of power or authority between the entities involved.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa7be288190983f13e9c7061b6d |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.