Triple
T18924566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference of the Parties to the WHO FCTC |
E462941
|
entity |
| Predicate | observerType |
P2277
|
FINISHED |
| Object | non‑Party States |
—
|
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: non‑Party States | Statement: [Conference of the Parties to the WHO FCTC, observerType, non‑Party States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observerType Context triple: [Conference of the Parties to the WHO FCTC, observerType, non‑Party States]
-
A.
observerStatusIn
chosen
Indicates that an entity’s status or role is defined or valid within a specified observational context, system, or environment.
-
B.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
C.
observerState
Indicates the condition, status, or configuration an observer is in at the time it perceives or monitors something.
-
D.
observerDependent
Indicates that the truth, value, or manifestation of something varies depending on which observer is considering or measuring it.
-
E.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9b77c188190b2274ef45d538508 |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.