Triple
T23271518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Longstop Hill |
E588302
|
entity |
| Predicate | combatant |
P375
|
FINISHED |
| Object | Axis forces |
—
|
NE NERFINISHED |
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: Axis forces | Statement: [Battle of Longstop Hill, combatant, Axis forces]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Axis forces Context triple: [Battle of Longstop Hill, combatant, Axis forces]
-
A.
Axis
Axis is a record label imprint associated with the independent British label 4AD, used for releasing selected music projects under its brand.
-
B.
Axis
Axis is an amusement park ride located in Adventure Island, known for providing thrilling, high-energy motion to its riders.
-
C.
Axis
chosen
Axis refers to the World War II military coalition of Germany, Italy, Japan, and their allies that opposed the Allied powers.
-
D.
Center Force
Center Force was the main Japanese naval task force under Vice Admiral Takeo Kurita during the Battle of Leyte Gulf in World War II, composed largely of battleships and heavy cruisers.
-
E.
Home Forces
Home Forces was the British Army command responsible for the defense and military organization of the United Kingdom during the World Wars.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957418fc819085ee528622e0c6de |
completed | April 29, 2026, 5:21 a.m. |
Created at: April 17, 2026, 4:46 p.m.