Triple
T6314905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seediq people |
E141590
|
entity |
| Predicate | mediaRepresentationType |
P17824
|
FINISHED |
| Object | Film |
—
|
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: Film | Statement: [Seediq people, mediaRepresentationType, Film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaRepresentationType Context triple: [Seediq people, mediaRepresentationType, Film]
-
A.
mediaAppearanceType
Indicates the specific kind or category of media appearance associated with an entity (e.g., interview, feature, cameo, or performance).
-
B.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
C.
mediaDepictionAs
chosen
Indicates that one entity is portrayed or represented as another entity or in a particular way within some medium (e.g., image, film, text).
-
D.
mediaDependentInterface
Indicates that one interface or interaction is contingent on, or varies according to, the characteristics or type of the media involved.
-
E.
mediaName
Indicates the name or title assigned to a media item (such as a work, file, or publication) in the relationship.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064a197488190946c4637b3c829a5 |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.