Triple
T17317783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Blanding |
E420473
|
entity |
| Predicate | WWIIFunction |
P105707
|
FINISHED |
| Object | training U.S. Army infantry soldiers |
—
|
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: training U.S. Army infantry soldiers | Statement: [Camp Blanding, WWIIFunction, training U.S. Army infantry soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WWIIFunction Context triple: [Camp Blanding, WWIIFunction, training U.S. Army infantry soldiers]
-
A.
battlefieldFunction
Indicates the role or purpose an entity serves within a combat or battlefield context, such as its tactical or operational function during warfare.
-
B.
functionInWarfare
chosen
Indicates the role, purpose, or operational function that something serves within a military or warfare context.
-
C.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
-
D.
WWIIUse
Indicates that one entity made use of another entity during World War II, typically for military, strategic, or wartime-related purposes.
-
E.
WWIITheater
Indicates the geographic or operational theater in which a World War II-related event, action, or entity was involved.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399ea7dc8190a0ecab7534fe16c3 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.