Triple
T29611881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amon Göth |
E754747
|
entity |
| Predicate | laterDetainedBy |
P6463
|
FINISHED |
| Object | United States forces |
—
|
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 forces | Statement: [Amon Göth, laterDetainedBy, United States forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDetainedBy Context triple: [Amon Göth, laterDetainedBy, United States forces]
-
A.
detainedBy
chosen
Indicates that an entity is being held in custody or confinement by another entity, typically an authority or controlling party.
-
B.
detainedAfter
Indicates that one entity is held in custody or confinement following another specified event or action.
-
C.
detainedFor
Indicates that one entity is being held in custody or confinement because of, or as a consequence of, another entity (such as a reason, charge, or event).
-
D.
detainedAs
Indicates that one entity is held in custody in the capacity or role specified by another entity (e.g., as a suspect, witness, or specific status).
-
E.
wasDetainedDuring
Indicates that an entity was held in custody or confinement for some period of time during a specified event or time interval.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: April 28, 2026, 6:29 p.m.