Triple
T681054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood and Sand (1922 film) |
E13180
|
entity |
| Predicate | hasPosterTagline |
P7688
|
FINISHED |
| Object | The supreme drama of the bull ring |
—
|
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: The supreme drama of the bull ring | Statement: [Blood and Sand (1922 film), hasPosterTagline, The supreme drama of the bull ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPosterTagline Context triple: [Blood and Sand (1922 film), hasPosterTagline, The supreme drama of the bull ring]
-
A.
hasFilmPoster
Indicates that one entity serves as the film poster associated with another film entity.
-
B.
hasTagline
chosen
Indicates that an entity is associated with a specific slogan or tagline that represents or promotes it.
-
C.
hasIMDbId
Indicates that an entity is associated with a specific identifier used by the Internet Movie Database (IMDb) to uniquely reference it.
-
D.
servedInTheatres
Indicates that a film or performance was publicly exhibited in movie theaters or similar cinema venues.
-
E.
hasBoxOffice
Indicates that an entity (typically a film or performance) has a specific box office revenue amount or record associated with it.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a06e294c8190873116a3253e04f9 |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1d79608190a849ba9ffad2879d |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.