Triple
T4582320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 21st Conference of the Parties |
E101882
|
entity |
| Predicate | numberOfParticipatingParties |
P1131
|
FINISHED |
| Object | 196 |
—
|
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: 196 | Statement: [21st Conference of the Parties, numberOfParticipatingParties, 196]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfParticipatingParties Context triple: [21st Conference of the Parties, numberOfParticipatingParties, 196]
-
A.
hasNumberOfParties
Indicates the total count of distinct parties or participants involved in a given relationship, agreement, or event.
-
B.
opposingParticipants
Indicates that the related entities are participants positioned in opposition to each other within the same interaction, event, or context.
-
C.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
-
D.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
-
E.
numberOfParticipants
chosen
Indicates the total count of entities involved in a particular event, activity, or relationship.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59029568819091db1e77a9a2ec41 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.