Triple
T11317658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anatevka |
E268006
|
entity |
| Predicate | plotEventLocation |
P49732
|
FINISHED |
| Object | wedding of Tzeitel and Motel |
—
|
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: wedding of Tzeitel and Motel | Statement: [Anatevka, plotEventLocation, wedding of Tzeitel and Motel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plotEventLocation Context triple: [Anatevka, plotEventLocation, wedding of Tzeitel and Motel]
-
A.
plotLocation
Indicates the relationship between a creative work and the place or setting where its story or events occur.
-
B.
locationOfEventDescribed
chosen
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
C.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
D.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
E.
triggerEventLocation
Indicates the location where a triggering event occurs or is initiated.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c3cf748190987838029d9f7fff |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.