Triple
T36060583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boxer Santaros |
E1043065
|
entity |
| Predicate | inUniverseGenreOfWork |
P146635
|
FINISHED |
| Object | action 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: action film | Statement: [Boxer Santaros, inUniverseGenreOfWork, action film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseGenreOfWork Context triple: [Boxer Santaros, inUniverseGenreOfWork, action film]
-
A.
inUniverseGenre
Indicates that a work’s genre classification exists within the fictional universe itself (e.g., as an in-story show, book, or media type), rather than being an external, real-world genre label.
-
B.
hasGenreOfWorkItAppearsIn
chosen
Indicates that an entity is associated with the genre of the work in which it appears.
-
C.
workAuthoredInUniverse
Indicates that a creative work is set within, or narratively belongs to, a particular fictional or conceptual universe.
-
D.
genreOfWorkContributedTo
Indicates that an entity contributed to a work belonging to a specified genre.
-
E.
genreOfWorkDescribedIn
Indicates that a work is characterized as belonging to a particular genre as described in another resource or context.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:08 p.m.