Triple
T34673449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimberley Process Certification Scheme |
E890437
|
entity |
| Predicate | negotiationsBeganIn |
P5755
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Kimberley Process Certification Scheme, negotiationsBeganIn, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: negotiationsBeganIn Context triple: [Kimberley Process Certification Scheme, negotiationsBeganIn, 2000]
-
A.
negotiationStartYear
chosen
Indicates the calendar year in which a negotiation process between parties was initiated.
-
B.
negotiationStart
Indicates the point in time or event at which a negotiation process between parties begins.
-
C.
negotiationAssociatedWith
Indicates a relationship where a negotiation is connected to, involves, or is conducted by a particular entity (such as a person, organization, or group).
-
D.
negotiatesBetween
Indicates a relationship where an entity acts as an intermediary to facilitate negotiation or mediation between two other entities.
-
E.
negotiatedAtConference
Indicates that the entities reached or conducted a negotiation during a specific conference.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72322256c8190afb14d73a2612b6f |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.