Triple
T26912935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirk Van Saene |
E677437
|
entity |
| Predicate | collectiveMemberWith |
P73984
|
FINISHED |
| Object | Dries Van Noten |
—
|
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: Dries Van Noten | Statement: [Dirk Van Saene, collectiveMemberWith, Dries Van Noten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveMemberWith Context triple: [Dirk Van Saene, collectiveMemberWith, Dries Van Noten]
-
A.
coMemberWith
chosen
Indicates that two or more entities share membership in the same group, organization, or collective.
-
B.
eachMemberHas
Indicates that every individual element within a group or collection possesses or is associated with a specified property, attribute, or item.
-
C.
killsMembersOf
Indicates that one entity causes the death of individuals who belong to a particular group or organization.
-
D.
includedMembersOf
Indicates that certain members or elements are contained within, or form part of, a specified group or collection.
-
E.
identifiesMembersBy
Indicates that one entity specifies or determines the individual members that belong to another entity or group.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 6:02 a.m.