Triple
T17347814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Janiculum (1849) |
E421728
|
entity |
| Predicate | foughtOnTerrain |
P127128
|
FINISHED |
| Object | hilltop positions |
—
|
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: hilltop positions | Statement: [Battle of the Janiculum (1849), foughtOnTerrain, hilltop positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtOnTerrain Context triple: [Battle of the Janiculum (1849), foughtOnTerrain, hilltop positions]
-
A.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
B.
battleTypeAtSite
Indicates the specific type or category of battle that occurred at a given site.
-
C.
battleBelligerentAtSite
Indicates that a particular belligerent (participant in a battle) was present and engaged in that battle at a specified site or location.
-
D.
foughtInCountry
Indicates that an entity participated in a fight, battle, or war that took place within the specified country.
-
E.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2a2ee48190976732e654a40053 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.