Triple
T1885276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States Parties to the Rome Statute |
E39948
|
entity |
| Predicate | includesEntityType |
P16833
|
FINISHED |
| Object | sovereign state |
—
|
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: sovereign state | Statement: [States Parties to the Rome Statute, includesEntityType, sovereign state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEntityType Context triple: [States Parties to the Rome Statute, includesEntityType, sovereign state]
-
A.
documentedEntityType
chosen
Indicates that an entity has been documented as belonging to a specific type or category.
-
B.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
C.
appliesToTerritorialEntity
Indicates that something (such as a rule, measure, status, or attribute) is valid for, relevant to, or in effect within a specific territorial entity.
-
D.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.