Triple
T31622231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Part 2 of the Rome Statute |
E806925
|
entity |
| Predicate | adoptedWithStatuteOn |
P3076
|
FINISHED |
| Object | 17 July 1998 |
—
|
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: 17 July 1998 | Statement: [Part 2 of the Rome Statute, adoptedWithStatuteOn, 17 July 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedWithStatuteOn Context triple: [Part 2 of the Rome Statute, adoptedWithStatuteOn, 17 July 1998]
-
A.
adoptedAt
chosen
Indicates the time or date at which an adoption event took place.
-
B.
adoptedPursuantTo
Indicates that something (such as a measure, policy, or decision) was formally adopted in accordance with, and on the basis of, a specific legal authority, procedure, or instrument.
-
C.
adoptedAfter
Indicates that one entity was adopted at a later time than another entity.
-
D.
adoptedThrough
Indicates that an adoption relationship was established or carried out by means of a specified process, channel, or intermediary.
-
E.
adoptedWith
Indicates that two or more entities were adopted at the same time or as part of the same adoption event or process.
- 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_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 30, 2026, 10:41 p.m.