Triple
T30162176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lex Manilia |
E766696
|
entity |
| Predicate | replacedCommander |
P80178
|
FINISHED |
| Object | Lucullus |
—
|
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: Lucullus | Statement: [Lex Manilia, replacedCommander, Lucullus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedCommander Context triple: [Lex Manilia, replacedCommander, Lucullus]
-
A.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
B.
changeOfCommand
chosen
Indicates a transfer of authority or control from one entity to another, typically marking a formal shift in leadership or responsibility.
-
C.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
D.
sideCommander
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
-
E.
commanderAffected
Indicates that a commander experiences an impact, influence, or change as a result of a particular event, action, or condition.
- 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_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 29, 2026, 7:22 p.m.