Triple
T35600869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraunhofer Group for Microelectronics |
E1028757
|
entity |
| Predicate | hasMemberInstitute |
P3814
|
FINISHED |
| Object | Fraunhofer IZM |
—
|
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: Fraunhofer IZM | Statement: [Fraunhofer Group for Microelectronics, hasMemberInstitute, Fraunhofer IZM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberInstitute Context triple: [Fraunhofer Group for Microelectronics, hasMemberInstitute, Fraunhofer IZM]
-
A.
hasMemberSociety
Indicates that an organization or group includes a specific society as one of its constituent members.
-
B.
hasInstitutionalHome
Indicates that an entity is formally based in, hosted by, or affiliated with a particular institution as its organizational home.
-
C.
includesInstitution
chosen
Indicates that one entity contains, encompasses, or has as a member a particular institution.
-
D.
hasInstitutions
Indicates that one entity possesses, contains, or is associated with one or more institutions.
-
E.
hasMemberOrganizationsIn
Indicates that an entity includes or comprises member organizations that are located in or associated with a specified place or region.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: May 3, 2026, 4:05 p.m.