Triple
T32851421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Avaricum |
E840261
|
entity |
| Predicate | defensiveStrategyOfGauls |
P180997
|
FINISHED |
| Object | scorched earth policy |
—
|
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: scorched earth policy | Statement: [Siege of Avaricum, defensiveStrategyOfGauls, scorched earth policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveStrategyOfGauls Context triple: [Siege of Avaricum, defensiveStrategyOfGauls, scorched earth policy]
-
A.
roleInGallicWars
Indicates the role or involvement an entity had in the events or campaigns of the Gallic Wars.
-
B.
GallicCommander
Indicates a person who holds a commanding or leadership role over Gallic forces or within a Gallic context.
-
C.
approximateGallicStrength
Indicates an estimation or rough calculation of the level or magnitude of Gallic strength in a given context.
-
D.
resultAtBattleOfArausio
Indicates that an entity is the outcome or consequence of the Battle of Arausio.
-
E.
NerviiForcesCommandedBy
Indicates that a specified individual or entity holds command authority over the Nervii forces.
- F. None of above. chosen
Provenance (4 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: May 1, 2026, 1:17 a.m.