Triple
T410296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Covenant on Economic, Social and Cultural Rights |
E9473
|
entity |
| Predicate | optionalProtocolAdoptedDate |
P3399
|
FINISHED |
| Object | 2008-12-10 |
—
|
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: 2008-12-10 | Statement: [International Covenant on Economic, Social and Cultural Rights, optionalProtocolAdoptedDate, 2008-12-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optionalProtocolAdoptedDate Context triple: [International Covenant on Economic, Social and Cultural Rights, optionalProtocolAdoptedDate, 2008-12-10]
-
A.
conventionAdoptedAt
Indicates that a convention was formally adopted or agreed upon at a specific event, meeting, or location.
-
B.
developedAt
Indicates the place or location where something was created, built, or developed.
-
C.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
D.
dateAdopted
chosen
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
-
E.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.