Triple
T25465704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Women’s Forum |
E638164
|
entity |
| Predicate | hasGlobalProgram |
P4561
|
FINISHED |
| Object | Leadership Foundation |
—
|
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: Leadership Foundation | Statement: [International Women’s Forum, hasGlobalProgram, Leadership Foundation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlobalProgram Context triple: [International Women’s Forum, hasGlobalProgram, Leadership Foundation]
-
A.
hasGlobalProgramme
chosen
Indicates that an entity operates, participates in, or is associated with a programme that is implemented or recognized at a global or international level.
-
B.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
C.
hasGlobalPlan
Indicates that an entity possesses or is associated with an overarching, comprehensive plan that applies at a global or system-wide level.
-
D.
hasComponentProgram
Indicates that one program includes or is composed of another program as a component or sub-program.
-
E.
hasCalledProgram
Indicates that one program has invoked or executed another program.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f74c5df88190a683cddba03a7afe |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:14 p.m.