Triple
T10887803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunga Ridge |
E257093
|
entity |
| Predicate | strategicObjectiveForJapan |
P19747
|
FINISHED |
| Object | recapture of Henderson Field |
—
|
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: recapture of Henderson Field | Statement: [Lunga Ridge, strategicObjectiveForJapan, recapture of Henderson Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicObjectiveForJapan Context triple: [Lunga Ridge, strategicObjectiveForJapan, recapture of Henderson Field]
-
A.
objectiveOfJapaneseForces
chosen
Indicates that a specified target, goal, or aim is the military objective pursued by Japanese forces.
-
B.
strategicObjectiveInBurma
Indicates that an entity has or represents a strategic objective specifically related to Burma (Myanmar).
-
C.
strategicGoal
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
-
D.
strategicObjectiveAfghan
Indicates that an entity has a strategic objective specifically related to Afghanistan or Afghan affairs.
-
E.
strategicObjectiveSpain
Indicates that an entity has a strategic objective specifically related to Spain.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75201e6888190a2bc41a17784eec3 |
completed | April 9, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.