Triple
T33140007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truk Islands |
E848117
|
entity |
| Predicate | wasMajorBaseDuring |
P176136
|
FINISHED |
| Object | World War II |
E32
|
NE 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: World War II | Statement: [Truk Islands, wasMajorBaseDuring, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorBaseDuring Context triple: [Truk Islands, wasMajorBaseDuring, World War II]
-
A.
wasMajorCenterDuring
Indicates that a place served as a primary or highly significant hub of activity, influence, or importance during a specified time period.
-
B.
isMajorBaseIn
Indicates that a location serves as a primary or central base of operations within a specified area or organization.
-
C.
hasMajorUSBase
Indicates that a location hosts a significant United States military base or installation.
-
D.
hasMajorBaseAmong
Indicates that one entity has its primary or most significant base of operations located within or among another entity or group.
-
E.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
- F. None of above. chosen
Provenance (5 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35160e78208190857689ea9ee08a8a |
completed | June 19, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:28 a.m.