Triple
T4427045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antipater the Idumaean |
E95233
|
entity |
| Predicate | gainedPowerThrough |
P47765
|
FINISHED |
| Object | Roman patronage |
—
|
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: Roman patronage | Statement: [Antipater the Idumaean, gainedPowerThrough, Roman patronage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedPowerThrough Context triple: [Antipater the Idumaean, gainedPowerThrough, Roman patronage]
-
A.
methodOfGainingPower
chosen
Indicates the way or process through which an entity acquires or increases power.
-
B.
regainedPowerIn
Indicates that an entity has recovered or reestablished its previous level of power, control, or authority within a specified context or domain.
-
C.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
D.
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.
-
E.
powerLevel
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554fb28081909018eaecc0c5c230 |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.