Triple
T16458449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gull Force |
E399742
|
entity |
| Predicate | treatmentAsPOWs |
P115931
|
FINISHED |
| Object | harsh conditions |
—
|
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: harsh conditions | Statement: [Gull Force, treatmentAsPOWs, harsh conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatmentAsPOWs Context triple: [Gull Force, treatmentAsPOWs, harsh conditions]
-
A.
treatmentOfSovietPOWs
Indicates how individuals, groups, or authorities behaved toward, managed, or dealt with Soviet prisoners of war.
-
B.
prisonersOfWar
Indicates a relationship where certain individuals are held in custody by an enemy during an armed conflict as prisoners of war.
-
C.
treatmentOfInternees
chosen
Indicates how individuals who are interned or detained are handled, managed, or treated by the responsible authorities or entities.
-
D.
UnionPrisonersTaken
Indicates that Union forces captured and held individuals as prisoners.
-
E.
captivesTaken
Indicates that one entity has taken another entity or group into captivity, holding them against their will.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d7ef5cc819084cfeb1a3e39d3cc |
completed | April 18, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.