Triple
T27868515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einstein |
E704425
|
entity |
| Predicate | appearsInFranchiseMediaType |
P795
|
FINISHED |
| Object | feature film trilogy |
—
|
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: feature film trilogy | Statement: [Einstein, appearsInFranchiseMediaType, feature film trilogy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInFranchiseMediaType Context triple: [Einstein, appearsInFranchiseMediaType, feature film trilogy]
-
A.
mediaFranchiseType
Indicates the specific kind or category of media franchise that an entity belongs to (e.g., film series, TV franchise, game franchise).
-
B.
portrayedInFranchise
Indicates that an entity is depicted as a character or element within a specific media franchise.
-
C.
hasMediaFranchise
Indicates that one entity is part of, or belongs to, a larger media franchise represented by another entity.
-
D.
appearsIn
chosen
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
E.
mediaFranchiseDerivedFrom
Indicates that one media franchise originates from, is based on, or was developed from another pre-existing work or franchise.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 6:22 p.m.