Triple
T26935419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesseract |
E678363
|
entity |
| Predicate | prominentAppearanceSeries |
P26455
|
FINISHED |
| Object | Loki (TV series) |
—
|
NE NERFINISHED |
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: Loki (TV series) | Statement: [Tesseract, prominentAppearanceSeries, Loki (TV series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentAppearanceSeries Context triple: [Tesseract, prominentAppearanceSeries, Loki (TV series)]
-
A.
prominentAppearanceFilm
Indicates that an entity has a major or highly visible role or presence in a particular film.
-
B.
hasProminentSeries
Indicates that an entity is notably associated with a major or well-known series as a defining feature.
-
C.
notablePerformanceSeries
Indicates a recurring set of performances or appearances by an entity that are recognized as particularly significant or noteworthy.
-
D.
appearsInSeriesBy
Indicates that one entity (such as a work or character) is featured within a series that is created, authored, or produced by another entity.
-
E.
appearsInSeries
chosen
Indicates that an entity is featured or occurs within a particular series.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 6:15 a.m.