Triple
T33522004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunga Point |
E858528
|
entity |
| Predicate | frontDuring |
P117051
|
FINISHED |
| Object | Solomon Islands campaign |
—
|
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: Solomon Islands campaign | Statement: [Lunga Point, frontDuring, Solomon Islands campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontDuring Context triple: [Lunga Point, frontDuring, Solomon Islands campaign]
-
A.
frontIn
Indicates that one entity is positioned directly in front of another entity in space or sequence.
-
B.
frontOf
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
C.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
D.
frontUsed
Indicates that the front side or front-facing part of an entity is utilized or engaged in performing an action or function in relation to another entity.
-
E.
frontLineDuring
chosen
Indicates that an entity is positioned at or serves on the front line during a specified time or event.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.