Triple
T30319935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Vipsanius Agrippa |
E771171
|
entity |
| Predicate | militaryAdvisorTo |
P12244
|
FINISHED |
| Object | Augustus |
—
|
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: Augustus | Statement: [Marcus Vipsanius Agrippa, militaryAdvisorTo, Augustus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryAdvisorTo Context triple: [Marcus Vipsanius Agrippa, militaryAdvisorTo, Augustus]
-
A.
hasMilitaryAdvisor
chosen
Indicates that one entity serves as a military advisor to another, providing guidance or expertise on military matters.
-
B.
militaryDirector
Indicates that one entity serves as the military director or chief military authority for another entity.
-
C.
warSecretary
Indicates that one entity serves as the war secretary (or secretary of war/defense) of another entity, typically a government or state.
-
D.
hasMilitaryAdvisorTitle
Indicates that an entity holds or is assigned a formal title designating them as a military advisor.
-
E.
coordinatesMilitaryPolicyWith
Indicates that one entity aligns, harmonizes, or jointly plans its military policies or strategies with another entity.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 7:52 p.m.