Triple
T17734731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutaguchi Renya |
E442682
|
entity |
| Predicate | detainingPower |
P6463
|
FINISHED |
| Object | Allied forces |
—
|
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: Allied forces | Statement: [Mutaguchi Renya, detainingPower, Allied forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detainingPower Context triple: [Mutaguchi Renya, detainingPower, Allied forces]
-
A.
detainsUnder
Indicates that one entity holds another in custody or confinement under a specific legal authority, provision, or condition.
-
B.
detainedBy
chosen
Indicates that an entity is being held in custody or confinement by another entity, typically an authority or controlling party.
-
C.
usedToDetain
Indicates that something serves or functioned as a means, tool, or facility for holding or confining someone against their will.
-
D.
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).
-
E.
detainsOnBehalfOf
Indicates that one party holds or keeps another party in custody or confinement acting under the authority, instruction, or representation of a different party.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e98a00819089490be2aa36873d |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.