Triple
T10811854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaffar |
E255119
|
entity |
| Predicate | hasNotableWorkRelation |
P61425
|
FINISHED |
| Object | Conrad Veidt filmography |
—
|
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: Conrad Veidt filmography | Statement: [Jaffar, hasNotableWorkRelation, Conrad Veidt filmography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableWorkRelation Context triple: [Jaffar, hasNotableWorkRelation, Conrad Veidt filmography]
-
A.
hasNotableWorkExample
chosen
Indicates that an entity has a specific notable work cited as an example associated with it.
-
B.
hasNotableWorkSetThere
Indicates that a notable work (such as a book, film, or other creative piece) is set in or takes place within the referenced location.
-
C.
hasCatalogedWorkOn
Indicates that an entity has formally recorded, listed, or documented another entity as a work within a catalog or collection.
-
D.
hasNotableWorkCategory
Indicates that an entity’s notable work belongs to, or is classified under, a particular category or type.
-
E.
hasWorksAbout
Indicates that one entity (such as a creator, collection, or source) includes or is associated with works whose subject or focus is another entity.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733eadda48190b2b1183ee60102cb |
completed | April 9, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.