Triple
T22622158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grumman Widgeon |
E558310
|
entity |
| Predicate | primaryUseDuringWWII |
P10702
|
FINISHED |
| Object | anti‑submarine patrol |
—
|
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: anti‑submarine patrol | Statement: [Grumman Widgeon, primaryUseDuringWWII, anti‑submarine patrol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseDuringWWII Context triple: [Grumman Widgeon, primaryUseDuringWWII, anti‑submarine patrol]
-
A.
primaryUseLateWar
Indicates that something was used primarily during the later phase of a war, rather than in its early or middle stages.
-
B.
WWIIUse
chosen
Indicates that one entity made use of another entity during World War II, typically for military, strategic, or wartime-related purposes.
-
C.
frontDuringWWII
Indicates that an entity served as a military front or active combat theater during World War II.
-
D.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
E.
armamentWWII
Indicates that an entity served as a weapon, piece of equipment, or military hardware used during World War II.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3ad6f48190b351a52e4b1d9b2d |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3 p.m.