Triple
T30172511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pact of Misenum (39 BC) |
E766956
|
entity |
| Predicate | requiredActionFrom |
P10395
|
FINISHED |
| Object | Sextus Pompeius |
—
|
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: Sextus Pompeius | Statement: [Pact of Misenum (39 BC), requiredActionFrom, Sextus Pompeius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredActionFrom Context triple: [Pact of Misenum (39 BC), requiredActionFrom, Sextus Pompeius]
-
A.
requiredAction
Indicates that a specific action must be performed or fulfilled as a necessary condition in the given context.
-
B.
requiresActionFrom
chosen
Indicates that one entity is obligated to perform or initiate some action in response to or as a consequence of another entity or situation.
-
C.
forcedActionDescribedIn
Indicates that an action was carried out under compulsion or coercion as described in a particular source or description.
-
D.
promptedAction
Indicates that one entity initiates or triggers another entity to perform a specific action.
-
E.
expectedAction
Indicates that a particular action is anticipated or required to occur in a given context or scenario.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 29, 2026, 7:24 p.m.