Triple
T22655207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marat/Sade (stage production) |
E559204
|
entity |
| Predicate | stagedIn |
P149081
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Marat/Sade (stage production), stagedIn, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stagedIn Context triple: [Marat/Sade (stage production), stagedIn, 1960s]
-
A.
staging
Indicates the process of arranging, organizing, or setting up elements in preparation for a main event, performance, or deployment.
-
B.
stagedBy
Indicates that an event, performance, or production is organized, directed, or put on by a particular agent or entity.
-
C.
firstStagedIn
Indicates the place, venue, or context where a performance, play, or production was originally staged for the first time.
-
D.
isStagedBy
Indicates that something (such as a performance, event, or production) is organized, directed, or put on by a particular agent or entity.
-
E.
stagedWorkBy
Indicates that a particular staging or production of a work (such as a play, opera, or performance) was created, directed, or otherwise realized by a specific person or organization.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765a97ac819095f21ccbdada1d0a |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:06 p.m.