Triple
T23586844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavutu |
E582368
|
entity |
| Predicate | wasStrategicSiteDuring |
P46035
|
FINISHED |
| Object | World War II |
—
|
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: World War II | Statement: [Gavutu, wasStrategicSiteDuring, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasStrategicSiteDuring Context triple: [Gavutu, wasStrategicSiteDuring, World War II]
-
A.
wasMilitaryBaseDuring
Indicates that a location functioned as a military base during a specified time period or event.
-
B.
hasMilitarySignificanceSince
Indicates that something has held military importance or strategic value starting from a specified point in time.
-
C.
wasLandingSiteDuring
Indicates that a location served as the landing site for a particular event, mission, or vehicle during a specified time or context.
-
D.
wasKeyBattlegroundDuring
chosen
Indicates that a location served as an important site of conflict or struggle during a specified event or period.
-
E.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03195748190b7e34f334902ac93 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:41 p.m.