Triple
T33045688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decision 1/CP.13 |
E845591
|
entity |
| Predicate | COPSession |
P43094
|
FINISHED |
| Object | COP13 |
—
|
NE NERFINISHED |
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: COP13 | Statement: [Decision 1/CP.13, COPSession, COP13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: COPSession Context triple: [Decision 1/CP.13, COPSession, COP13]
-
A.
sessionOf
chosen
Indicates that one entity is a session that belongs to, occurs within, or is associated with another entity (such as an event, course, or meeting series).
-
B.
sessionConvenedBy
Indicates that a particular session is organized, initiated, or formally brought together by a specified agent or authority.
-
C.
IOCSessionLocation
Indicates the place or venue where an IOC session or meeting is held.
-
D.
sessionContext
Indicates the contextual relationship in which a session occurs, including its surrounding conditions, parameters, or environment that shape or influence that session.
-
E.
sessionOpenedBy
Indicates that a particular session was initiated or started by a specific entity.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.