Triple
T7084682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ichigaya Court, Tokyo |
E165044
|
entity |
| Predicate | trialTypeHosted |
P74882
|
FINISHED |
| Object | war crimes trials |
—
|
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: war crimes trials | Statement: [Ichigaya Court, Tokyo, trialTypeHosted, war crimes trials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialTypeHosted Context triple: [Ichigaya Court, Tokyo, trialTypeHosted, war crimes trials]
-
A.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
B.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
C.
trialMode
Indicates that an entity is operating in a temporary, limited-capability trial state rather than in full or permanent mode.
-
D.
hostedShow
Indicates that one entity served as the host or presenter of a particular show or program involving the other entity.
-
E.
plannedToHost
Indicates that an entity had the intention or arrangement to host an event, activity, or gathering.
- F. None of above. chosen
Provenance (4 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e511535c819098f60de54930380f |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:40 p.m.