Triple
T26241799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torokina |
E656334
|
entity |
| Predicate | beachheadEstablishedBy |
P160393
|
FINISHED |
| Object | United States Marines |
—
|
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: United States Marines | Statement: [Torokina, beachheadEstablishedBy, United States Marines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beachheadEstablishedBy Context triple: [Torokina, beachheadEstablishedBy, United States Marines]
-
A.
wasAlliedLandingSiteIn
Indicates that a location served as a landing site used by Allied forces within a specified military operation, campaign, or conflict context.
-
B.
countryOfFirstDeployment
Indicates the country where something (such as equipment, technology, or a system) was first put into operational use or service.
-
C.
regionOfColonyFounded
Indicates the geographic region in which a particular colony was originally founded.
-
D.
establishedAsNavalBase
Indicates that a location was formally designated and put into use as a naval base.
-
E.
timeInUseAsBeachhead
Indicates the duration for which something is actively used or maintained as a beachhead or initial foothold position.
- F. None of above. chosen
Provenance (4 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60d8f7f9c8190bb8cb8f8ac4c0ca5 |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 9:03 p.m.