Triple
T9932450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Summit on the Information Society |
E192677
|
entity |
| Predicate | firstPhaseStartTime |
P51679
|
FINISHED |
| Object | 2003-12-10 |
—
|
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: 2003-12-10 | Statement: [World Summit on the Information Society, firstPhaseStartTime, 2003-12-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPhaseStartTime Context triple: [World Summit on the Information Society, firstPhaseStartTime, 2003-12-10]
-
A.
firstPhaseEndDate
Indicates the date on which the first phase of a process, project, or activity is completed or scheduled to end.
-
B.
secondPhaseStartDate
Indicates the date on which the second phase of a process, project, or activity begins.
-
C.
firstRunTimePeriod
Indicates the initial time span or interval during which something first occurs, operates, or is in effect.
-
D.
mainPhaseDate
Indicates the date on which the primary or main phase of an event, process, or project occurs or is scheduled.
-
E.
phase1OpeningDate
chosen
Indicates the date on which the first phase of a project, development, or initiative is officially opened or begins operation.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b7897081909b28189aa57af250 |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.