Triple
T23681314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entropy |
E585025
|
entity |
| Predicate | hasDirectorAsProtagonistAnalog |
P106880
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Entropy, hasDirectorAsProtagonistAnalog, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectorAsProtagonistAnalog Context triple: [Entropy, hasDirectorAsProtagonistAnalog, true]
-
A.
hasDirectorStar
chosen
Indicates that a person both directed and starred in the same work (e.g., film, show, or production).
-
B.
hasDirectorCameo
Indicates that the director of a work appears in a cameo role within that same work.
-
C.
hasDirectorOfWork
Indicates that an entity has a specific person or organization serving as the director responsible for overseeing its work or project.
-
D.
hasDirectorCreator
Indicates that an entity has a person or organization who directed or created it (e.g., a film’s director or a work’s creator).
-
E.
isDirectedBy
Indicates that one entity serves as the director or guiding authority responsible for the creation, management, or execution of another entity (such as a film, project, or organization).
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f835ec8190a7bdcfa48ad79cd5 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:51 p.m.