Triple
T12551911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extremities |
E300116
|
entity |
| Predicate | hasStageMedium |
P67214
|
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: [Extremities, hasStageMedium, live theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageMedium Context triple: [Extremities, hasStageMedium, live theatre]
-
A.
stageMedium
chosen
Indicates that a performance, event, or presentation is taking place using a particular medium or format as its primary means of staging.
-
B.
hasPageMedium
Indicates that a page or document is associated with a particular physical or digital medium through which it is presented or stored.
-
C.
hasMediumCharacter
Indicates that one entity possesses or is associated with a character whose size, intensity, or degree is classified as medium.
-
D.
hasRideMedium
Indicates that an entity’s ride or journey is conducted using a particular transportation medium or mode.
-
E.
hasAwardMedium
Indicates that an award is associated with a particular medium or format through which it is given or recognized.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:58 p.m.