Triple
T22403798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satish Alekar |
E553827
|
entity |
| Predicate | actedInMedium |
P54385
|
FINISHED |
| Object | 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: theatre | Statement: [Satish Alekar, actedInMedium, theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actedInMedium Context triple: [Satish Alekar, actedInMedium, theatre]
-
A.
occursInMedium
chosen
Indicates that an event, process, or interaction takes place within or is hosted by a particular medium or environment.
-
B.
mediatedIn
Indicates that an entity acted as an intermediary or facilitator in bringing about, enabling, or influencing another entity or event.
-
C.
introducedInMedium
Indicates that an entity first appears or is initially presented within a specified medium (such as a book, film, game, or other format).
-
D.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
-
E.
subsequentMedium
Indicates that one medium or format follows another in a sequence, typically as a later or alternative form of the same content or communication.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b6762c8190991fc14c5ca8e609 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.