Triple
T33490477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Issus |
E857723
|
entity |
| Predicate | battleClassification |
P115282
|
FINISHED |
| Object | decisive battle site |
—
|
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: decisive battle site | Statement: [Issus, battleClassification, decisive battle site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleClassification Context triple: [Issus, battleClassification, decisive battle site]
-
A.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
B.
battleScale
Indicates the relative size or intensity of a battle, such as how large, extensive, or severe the conflict is.
-
C.
battleTypeAtSite
chosen
Indicates the specific type or category of battle that occurred at a given site.
-
D.
battleRelatedTo
Indicates a relationship where one entity is connected to, associated with, or relevant to a particular battle or combat event.
-
E.
eraOfWarfare
Indicates a historical period characterized by significant or sustained warfare.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:38 a.m.