Triple
T26572009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirk De Jonge |
E666850
|
entity |
| Predicate | meetingOrganizer |
P161040
|
FINISHED |
| Object | Communist Party |
—
|
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: Communist Party | Statement: [Dirk De Jonge, meetingOrganizer, Communist Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingOrganizer Context triple: [Dirk De Jonge, meetingOrganizer, Communist Party]
-
A.
coOrganizer
Indicates a relationship where an entity jointly organizes an event, activity, or project together with one or more other organizers.
-
B.
meetingType
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
C.
plansMeetingWith
Indicates that one entity arranges or intends to organize a meeting involving another entity.
-
D.
meeting
Indicates that two or more entities come together at the same time and place for discussion, decision-making, or coordinated activity.
-
E.
meetingContext
Indicates the situational setting, circumstances, or background conditions in which a meeting takes place.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614a519f0819087c98f8b48d14cce |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 1:58 a.m.