Triple
T24439305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puntila |
E616214
|
entity |
| Predicate | firstPerformanceOfWorkLocation |
P138066
|
FINISHED |
| Object | Zürich |
—
|
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: Zürich | Statement: [Puntila, firstPerformanceOfWorkLocation, Zürich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceOfWorkLocation Context triple: [Puntila, firstPerformanceOfWorkLocation, Zürich]
-
A.
firstPerformanceLocationOfWorkAppearingIn
chosen
Indicates the location where a work was first performed or premiered.
-
B.
firstPerformancePlaceOfWork
Indicates the place of work where an entity had its first performance or debut.
-
C.
firstPerformanceCityOfWork
Indicates the city where a particular work was first performed.
-
D.
firstPerformanceOfWorkAppearedIn
Indicates that a given performance is the earliest known or documented performance in which a particular work was presented or appeared.
-
E.
firstPerformanceWork
Indicates that a performance is the debut or initial presentation of a particular work.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f297891f108190a98e55c900494d30 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.