Triple
T33581985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Magic Order |
E860171
|
entity |
| Predicate | announcedAdaptationType |
P1926
|
FINISHED |
| Object | television series |
—
|
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: television series | Statement: [The Magic Order, announcedAdaptationType, television series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedAdaptationType Context triple: [The Magic Order, announcedAdaptationType, television series]
-
A.
adaptedAs
chosen
Indicates that one work, concept, or entity has been transformed or re-created into another form or medium based on the original.
-
B.
notableAdaptationType
Indicates that one work is a significant adaptation of another work in a specific way or medium (e.g., film adaptation, stage adaptation).
-
C.
announcedAs
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by another entity.
-
D.
hasAdaptationsIn
Indicates that something possesses or exhibits adaptations within a particular context, environment, or domain.
-
E.
announcedFor
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:40 a.m.