Triple
T32307948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Additional Protocol providing for a system of collective complaints |
E825417
|
entity |
| Predicate | treatySeries |
P33308
|
FINISHED |
| Object | ETS No. 158 |
—
|
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: ETS No. 158 | Statement: [Additional Protocol providing for a system of collective complaints, treatySeries, ETS No. 158]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatySeries Context triple: [Additional Protocol providing for a system of collective complaints, treatySeries, ETS No. 158]
-
A.
resultOfTreaties
Indicates that something exists, occurs, or holds true as a consequence or outcome of one or more treaties.
-
B.
historicalTreaty
Indicates that a formal agreement or pact was established between entities at some point in the past.
-
C.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
D.
treatyFocus
chosen
Indicates that a treaty is primarily concerned with, directed toward, or centered on a particular subject, issue, or area.
-
E.
treatyFamily
Indicates that there exists a familial or kinship-based treaty or formal agreement relationship between the entities.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 12:45 a.m.