Triple
T7451017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Maidstone |
E172007
|
entity |
| Predicate | houseToHouseFighting |
P35675
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Battle of Maidstone, houseToHouseFighting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseToHouseFighting Context triple: [Battle of Maidstone, houseToHouseFighting, true]
-
A.
fightingOutOf
Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
-
B.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
-
C.
fightsAtLocation
Indicates that a fighting interaction between entities occurs at a specified location.
-
D.
methodOfCombat
chosen
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
E.
clanRival
Indicates a hostile or competitive relationship between two clans, typically involving ongoing conflict, opposition, or rivalry.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f38c28e08190956766a5222fe720 |
completed | March 27, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.