Triple
T28773460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman invasion of Egypt |
E726471
|
entity |
| Predicate | outcomeForRuler |
P167378
|
FINISHED |
| Object | Cleopatra VII loses her throne |
—
|
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: Cleopatra VII loses her throne | Statement: [Roman invasion of Egypt, outcomeForRuler, Cleopatra VII loses her throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForRuler Context triple: [Roman invasion of Egypt, outcomeForRuler, Cleopatra VII loses her throne]
-
A.
finalRuler
Indicates that an entity is the last or ultimate ruler of another entity, with no subsequent rulers following.
-
B.
concludedUnderRuler
Indicates that an event, agreement, or process was completed or finalized during the reign or authority of a specific ruler.
-
C.
governsOutcome
Indicates that one entity has decisive control or influence over the result or consequence affecting another entity.
-
D.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
E.
usedByRuler
Indicates that something is employed, utilized, or otherwise put to use by a ruler or governing authority.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:16 a.m.