Triple
T20224899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Social Forum |
E495352
|
entity |
| Predicate | CharterOfPrinciplesYear |
P24044
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [World Social Forum, CharterOfPrinciplesYear, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CharterOfPrinciplesYear Context triple: [World Social Forum, CharterOfPrinciplesYear, 2001]
-
A.
charterAdoptedIn
Indicates that a charter was formally adopted or enacted at a specific time or in a specific place.
-
B.
yearOfPromulgation
chosen
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
C.
charterEnteredIntoForce
Indicates that a charter has become legally effective and binding as of a specific point in time.
-
D.
yearEnteredIntoForce
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
-
E.
hasFoundingPrinciple
Indicates that one entity serves as the core founding principle or fundamental guiding tenet upon which another entity is established or based.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd8f1948190adbb947a7870bb43 |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.