Triple
T32696496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsi |
E836021
|
entity |
| Predicate | roleInSocialWar |
P108011
|
FINISHED |
| Object | leading insurgent people against Rome |
—
|
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: leading insurgent people against Rome | Statement: [Marsi, roleInSocialWar, leading insurgent people against Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSocialWar Context triple: [Marsi, roleInSocialWar, leading insurgent people against Rome]
-
A.
roleInWarOrConflict
chosen
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
B.
roleInTimeWar
Indicates that an entity held a specific role or function during the period or events referred to as the Time War.
-
C.
roleDuringConquest
Indicates the specific function, position, or capacity an entity held in relation to a particular conquest event.
-
D.
roleAfterWar
Indicates the role or position an entity assumes following the end of a war or armed conflict.
-
E.
roleInDespenserWar
Indicates the specific part or function an entity played in the events of the Despenser War.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a004fd3caf48190b2ec063a7bf0756b |
completed | May 10, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a004f7672dc8190aca91d1ed855bf9a |
completed | May 10, 2026, 9:27 a.m. |
Created at: May 1, 2026, 1:10 a.m.