Triple
T24969723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Piva Forks |
E624847
|
entity |
| Predicate | terrainControlledAfterBattle |
P28640
|
FINISHED |
| Object | high ground east of the Torokina beachhead |
—
|
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: high ground east of the Torokina beachhead | Statement: [Battle of the Piva Forks, terrainControlledAfterBattle, high ground east of the Torokina beachhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainControlledAfterBattle Context triple: [Battle of the Piva Forks, terrainControlledAfterBattle, high ground east of the Torokina beachhead]
-
A.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
B.
foughtOnTerrain
Indicates that an entity engaged in a fight or battle that took place on a specified type of terrain or ground.
-
C.
immediateAftermathLocation
Indicates the location where the direct and immediate consequences of an event take place.
-
D.
townControlled
Indicates that one entity has governing authority or administrative control over a town.
-
E.
heldTerritory
chosen
Indicates that one entity maintained control or possession over a specific territory or geographic area.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490283c481908c18246dc7125eec |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6 a.m.