Triple
T912998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Penelopiad |
E19703
|
entity |
| Predicate | mediumOfAdaptation |
P2375
|
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: [The Penelopiad, mediumOfAdaptation, theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediumOfAdaptation Context triple: [The Penelopiad, mediumOfAdaptation, theatre]
-
A.
adaptationType
chosen
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
B.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
-
C.
adaptedTo
Indicates that one entity has been modified, adjusted, or evolved to function effectively within the conditions, requirements, or characteristics defined by another entity.
-
D.
mediumOfOrigin
Indicates the original physical or digital medium from which an item, work, or data was derived or obtained.
-
E.
medium
Indicates that an entity serves as the means, channel, or intermediary through which an action, communication, or effect is carried out between other entities.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2f605bc8190a5245aa2ca55cf43 |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b2918ea881908698020b995a8eae |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.