Triple
T96393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rome Statute of the International Criminal Court |
E1940
|
entity |
| Predicate | articleCountApproximate |
P443
|
FINISHED |
| Object | 128 articles |
—
|
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: 128 articles | Statement: [Rome Statute of the International Criminal Court, articleCountApproximate, 128 articles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: articleCountApproximate Context triple: [Rome Statute of the International Criminal Court, articleCountApproximate, 128 articles]
-
A.
articleCount
chosen
Indicates the number of articles associated with a given entity or context.
-
B.
containsArticle
Indicates that one entity includes or holds an article (such as a written piece, item, or document) as part of its contents.
-
C.
numberOfStories
Indicates the total count of levels or floors that a structure or building has.
-
D.
collectionSize
Indicates the total number of items contained within a specified collection.
-
E.
article9Provision
Indicates a relationship where a specific legal or contractual element is identified as a provision contained within Article 9 of a larger document or agreement.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a250cb400c8190b56343bbe19b48c7 |
completed | Feb. 28, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69a24ebd19c48190bab291fea0ecc0c2 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.