Triple
T8682817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fortune Hunter |
E206077
|
entity |
| Predicate | sourceWorkMedium |
P18814
|
FINISHED |
| Object | theatrical play |
—
|
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: theatrical play | Statement: [The Fortune Hunter, sourceWorkMedium, theatrical play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceWorkMedium Context triple: [The Fortune Hunter, sourceWorkMedium, theatrical play]
-
A.
mediaWork
chosen
Indicates a relationship where one entity is a media-related work (such as a film, book, recording, or other creative media production) associated with another entity.
-
B.
repositoryMedium
Indicates the physical or digital medium through which a repository stores, maintains, or provides access to its contents.
-
C.
targetMedium
Indicates the medium or channel through which an action, message, or effect is directed or intended to be delivered.
-
D.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
E.
secondaryMedium
Indicates that an entity is associated with an additional, non-primary medium or channel through which it is expressed, delivered, or communicated.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae82e508190b0243328e98fcb1d |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.