Triple
T16858575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Social Forum 2013 |
E409849
|
entity |
| Predicate | hasPlenaries |
P21719
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [World Social Forum 2013, hasPlenaries, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlenaries Context triple: [World Social Forum 2013, hasPlenaries, yes]
-
A.
hasPlenarySessions
chosen
Indicates that an event or organization includes formal plenary sessions as part of its activities or structure.
-
B.
hasPlenaryChamber
Indicates that an institution or governing body possesses a designated plenary chamber where all members can meet and deliberate together.
-
C.
hasConferenceOfParties
Indicates that an entity is associated with or holds a Conference of the Parties (COP) as its formal decision-making or governing body.
-
D.
requiresForPlenary
Indicates that one entity must be present, completed, or satisfied as a prerequisite for another entity to proceed to or attain plenary (full or formal) status.
-
E.
hasParliamentarySession
Indicates that a governing body or legislature conducts or holds a formal parliamentary session.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37ef4748190b149d98fc0ab4205 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.