Triple
T18619529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COP15 Accord |
E455111
|
entity |
| Predicate | addressesParties |
P132423
|
FINISHED |
| Object | developed countries |
—
|
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: developed countries | Statement: [COP15 Accord, addressesParties, developed countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesParties Context triple: [COP15 Accord, addressesParties, developed countries]
-
A.
legalParties
Indicates that the related entities are formally recognized participants in a legal relationship, case, contract, or proceeding.
-
B.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
-
C.
componentParty
Indicates that one party functions as a constituent or member of a larger party or group within a composite relationship.
-
D.
namedPartyType
Indicates the specific role or category that a referenced party holds within a given context or relationship.
-
E.
partyNames
Indicates the names or identifiers of the entities (parties) involved in a particular relationship, agreement, or event.
- F. None of above. chosen
Provenance (4 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d07dc288190bb3b8b5ab06518da |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:46 a.m.