Triple
T26243744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETH Oberon compiler |
E656385
|
entity |
| Predicate | affiliationOfCreator |
P160396
|
FINISHED |
| Object | ETH Zurich |
—
|
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: ETH Zurich | Statement: [ETH Oberon compiler, affiliationOfCreator, ETH Zurich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliationOfCreator Context triple: [ETH Oberon compiler, affiliationOfCreator, ETH Zurich]
-
A.
employerOfCreator
Indicates that one entity is the employer of the entity that created another entity.
-
B.
composerAffiliation
Indicates that a composer is formally associated with, employed by, or otherwise connected to a particular organization, institution, or group.
-
C.
administrativeAffiliation
Indicates that one entity is formally connected to, governed by, or overseen by another entity within an administrative or organizational structure.
-
D.
studioAffiliation
Indicates a relationship where an entity is formally associated with, works for, or is produced by a particular studio.
-
E.
authorWorkCreator
Indicates that an entity is the creator (author) responsible for producing a particular work.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dc4aa808190ba3b5682944a7fb8 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 9:04 p.m.