Triple
T28410966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsic people |
E719659
|
entity |
| Predicate | leaderDuringSocialWar |
P11563
|
FINISHED |
| Object | Quintus Poppaedius Silo |
—
|
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: Quintus Poppaedius Silo | Statement: [Marsic people, leaderDuringSocialWar, Quintus Poppaedius Silo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderDuringSocialWar Context triple: [Marsic people, leaderDuringSocialWar, Quintus Poppaedius Silo]
-
A.
leaderDuring
Indicates that one entity serves as the leader of another entity during a specified time period.
-
B.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
-
C.
operatorDuringWar
Indicates that an entity operated or was active in its role during a time of war.
-
D.
belligerentLeader
chosen
Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
-
E.
goalDuringWar
Indicates that a particular goal or objective is pursued, exists, or is relevant during the time period of a war or armed conflict.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 1:26 a.m.