Triple
T35432037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landesring der Unabhängigen |
E1024087
|
entity |
| Predicate | notableFounderAffiliation |
P113921
|
FINISHED |
| Object | Migros |
E307487
|
NE 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: Migros | Statement: [Landesring der Unabhängigen, notableFounderAffiliation, Migros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFounderAffiliation Context triple: [Landesring der Unabhängigen, notableFounderAffiliation, Migros]
-
A.
notableCoFounderOccupation
Indicates that the co-founder is particularly notable or recognized for having a specific occupation.
-
B.
notableFounderMembership
chosen
Indicates that an entity is notably recognized as a founding member of another entity, such as an organization, group, or initiative.
-
C.
coFounderNotableFor
Indicates that a person is a co-founder of something for which they are notably recognized.
-
D.
notableFounderTeam
Indicates that the entity has a founding team whose members are particularly distinguished, prominent, or otherwise noteworthy.
-
E.
founderKnownFor
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
- F. None of above.
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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38cb75879c8190b9e7a87f8f5e59c7 |
completed | June 22, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.