Triple
T19780915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Popillius Laenas |
E475127
|
entity |
| Predicate | powerDisplayed |
P84381
|
FINISHED |
| Object | Roman hegemony in the eastern Mediterranean |
—
|
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 hegemony in the eastern Mediterranean | Statement: [Gaius Popillius Laenas, powerDisplayed, Roman hegemony in the eastern Mediterranean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerDisplayed Context triple: [Gaius Popillius Laenas, powerDisplayed, Roman hegemony in the eastern Mediterranean]
-
A.
showsPowerUse
chosen
Indicates that one entity demonstrates or exercises power, influence, or control over another entity or within a given context.
-
B.
powerDependsOn
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
-
C.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
D.
powerScope
Indicates the extent or domain within which an entity’s power, authority, or influence is valid or can be exercised.
-
E.
powerDirection
Indicates the direction in which power, influence, or control flows from one entity to another.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653846a248190adc4afe0dc29a402 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.