Triple
T30162198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lex Manilia |
E766696
|
entity |
| Predicate | extendedPreviousPowersOf |
P15177
|
FINISHED |
| Object | Pompey the Great |
—
|
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: Pompey the Great | Statement: [Lex Manilia, extendedPreviousPowersOf, Pompey the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedPreviousPowersOf Context triple: [Lex Manilia, extendedPreviousPowersOf, Pompey the Great]
-
A.
expandsPowersOf
chosen
Indicates that one entity increases, extends, or enhances the authority, capabilities, or influence held by another entity.
-
B.
successorPowers
Indicates that one entity has inherited authority, control, or responsibilities from another, functioning as its successor in power.
-
C.
expandedPowerTo
Indicates that one entity has increased or broadened authority, influence, or control over another entity or domain.
-
D.
exercisesPowersOf
Indicates that one entity actively uses, applies, or carries out the authority, rights, or powers granted to it over or in relation to another entity.
-
E.
roseToPowerIn
Indicates the point in time or context in which an entity gained authority, control, or a dominant position.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:22 p.m.