Triple
T19694166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emmanuel Pahud |
E472909
|
entity |
| Predicate | startTime (Berlin Philharmonic principal) |
P51709
|
FINISHED |
| Object | 1993 |
—
|
LITERAL 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: 1993 | Statement: [Emmanuel Pahud, startTime (Berlin Philharmonic principal), 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTime (Berlin Philharmonic principal) Context triple: [Emmanuel Pahud, startTime (Berlin Philharmonic principal), 1993]
-
A.
startTime (Duke of Bavaria)
Indicates the point in time at which the person began holding the title or office of Duke of Bavaria.
-
B.
chiefConductorStart
chosen
Indicates the time or event at which an individual begins serving as the chief conductor of an ensemble or organization.
-
C.
startTime (President of Germany)
Indicates the point in time at which a person’s term as President of Germany begins.
-
D.
startTime (Minister-President of Lower Saxony)
Indicates the point in time at which a person begins serving as Minister-President of Lower Saxony.
-
E.
startTime (Duke of Saxony)
Indicates the point in time at which the individual became the Duke of Saxony.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6421385e88190b22b12ab3d851dea |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.