Triple
T20359672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victims of Duty |
E496742
|
entity |
| Predicate | intendedPerformanceType |
P104495
|
FINISHED |
| Object | live theatre |
—
|
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: live theatre | Statement: [Victims of Duty, intendedPerformanceType, live theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedPerformanceType Context triple: [Victims of Duty, intendedPerformanceType, live theatre]
-
A.
intendedForPerformanceBy
Indicates that something (such as a work, role, or piece) is designed or meant to be performed by a particular performer or type of performer.
-
B.
intendedPerformanceMode
chosen
Indicates the manner or mode in which an action, process, or performance is meant or designed to be carried out.
-
C.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
-
D.
intendedOpeningUse
Indicates that an opening (such as a door, window, or passage) is designed or meant to be used for a particular purpose or function.
-
E.
intendedEngineType
Indicates that an entity is designed or specified to use a particular type of engine.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678573fc481908bf257e6ed41d750 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.