Triple
T25423000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatura |
E637033
|
entity |
| Predicate | internedGroups |
P163007
|
FINISHED |
| Object | prisoners of war during World War II |
—
|
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: prisoners of war during World War II | Statement: [Tatura, internedGroups, prisoners of war during World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internedGroups Context triple: [Tatura, internedGroups, prisoners of war during World War II]
-
A.
internedGroups
chosen
Indicates that certain groups of entities were confined or detained together, typically under restrictive or custodial conditions.
-
B.
impactedGroup
Indicates the group or population that is affected or influenced by a particular action, event, or condition.
-
C.
groupedInto
Indicates that multiple entities are collected or organized together as members of a common group or category.
-
D.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
E.
representedGroups
Indicates that an entity serves as an official or recognized representative for one or more groups.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 1:57 p.m.