Triple
T13598026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montevideo Convention on the Rights and Duties of States |
E324871
|
entity |
| Predicate | setsOutCriteriaFor |
P136
|
FINISHED |
| Object | 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: state | Statement: [Montevideo Convention on the Rights and Duties of States, setsOutCriteriaFor, state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsOutCriteriaFor Context triple: [Montevideo Convention on the Rights and Duties of States, setsOutCriteriaFor, state]
-
A.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
setsOut
Indicates that an entity begins a journey, course of action, or process, moving from an initial state or location toward a goal or destination.
-
C.
compositionCriterion
Indicates the rule or standard by which components are selected, combined, or arranged to form a whole.
-
D.
setsRulesFor
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
-
E.
evaluationCriteriaInclude
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0795acc8190a08667ab9dcb0d44 |
completed | April 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.