Triple
T31622294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | decisions of the International Criminal Court |
E806926
|
entity |
| Predicate | mayConcern |
P11116
|
FINISHED |
| Object | arrest warrants |
—
|
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: arrest warrants | Statement: [decisions of the International Criminal Court, mayConcern, arrest warrants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayConcern Context triple: [decisions of the International Criminal Court, mayConcern, arrest warrants]
-
A.
concern
chosen
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
B.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
C.
concernedSee
Indicates that one entity looks at or observes another with a sense of worry, care, or concern.
-
D.
concernsHypothesis
Indicates that something is about, relates to, or addresses a particular hypothesis.
-
E.
subjectOfConcernFor
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8af30288190afd82d3fe7d125f1 |
completed | May 3, 2026, 1:45 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:41 p.m.