Triple
T32517770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geneva Declaration of Principles |
E831103
|
entity |
| Predicate | phaseLocation |
P174543
|
FINISHED |
| Object | Geneva phase of WSIS |
—
|
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: Geneva phase of WSIS | Statement: [Geneva Declaration of Principles, phaseLocation, Geneva phase of WSIS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseLocation Context triple: [Geneva Declaration of Principles, phaseLocation, Geneva phase of WSIS]
-
A.
phaseIndicatedBy
Indicates that a particular phase or stage is determined, signaled, or specified by a given indicator or reference.
-
B.
phase
Indicates that one entity is in a particular stage, step, or phase within a process, sequence, or lifecycle relative to another reference.
-
C.
phaseType
Indicates the specific stage or phase category that an associated process, event, or lifecycle instance belongs to.
-
D.
phaseUsed
Indicates that a particular phase, stage, or step is utilized or applied in carrying out an action, process, or relationship.
-
E.
phaseCount
Indicates the number of distinct phases or stages associated with a given process, event, or entity.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4aabff08190ad437b687dd41f8d |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1 a.m.