Triple
T35293949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carroccio |
E1019304
|
entity |
| Predicate | locationOnBattlefield |
P94843
|
FINISHED |
| Object | center of the communal army |
—
|
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: center of the communal army | Statement: [Carroccio, locationOnBattlefield, center of the communal army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnBattlefield Context triple: [Carroccio, locationOnBattlefield, center of the communal army]
-
A.
battlefieldLocatedIn
Indicates that a battlefield is situated within or belongs to a specific geographic or administrative location.
-
B.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
C.
positionInBattle
chosen
Indicates the specific role or placement an entity occupies within the formation or structure of a battle.
-
D.
primaryBattlefieldOf
Indicates that a specified location serves as the main or most significant battlefield where a particular conflict or war primarily took place.
-
E.
locationOnField
Indicates the specific position or area that an entity occupies on a defined field or playing surface.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.