Triple
T3565834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choiseul Island |
E75444
|
entity |
| Predicate | notableWWIIAction |
P28183
|
FINISHED |
| Object | U.S. Marine Raiders diversionary raid in 1943 |
—
|
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: U.S. Marine Raiders diversionary raid in 1943 | Statement: [Choiseul Island, notableWWIIAction, U.S. Marine Raiders diversionary raid in 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWWIIAction Context triple: [Choiseul Island, notableWWIIAction, U.S. Marine Raiders diversionary raid in 1943]
-
A.
notableAirOperation
Indicates that there is a significant or historically important air operation associated with the subject.
-
B.
higherCommandDuringWWII
Indicates that one entity served as the superior military authority or command over another entity during World War II.
-
C.
notableForce
Indicates that an entity is recognized as a significant or influential force affecting another entity, system, or context.
-
D.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
E.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0a8f6288190928479f5bea32245 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.