Triple
T21839664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lestrange |
E539219
|
entity |
| Predicate | extendedCanonStatus |
P33854
|
FINISHED |
| Object | featured in Fantastic Beasts films |
—
|
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: featured in Fantastic Beasts films | Statement: [Lestrange, extendedCanonStatus, featured in Fantastic Beasts films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedCanonStatus Context triple: [Lestrange, extendedCanonStatus, featured in Fantastic Beasts films]
-
A.
inCanonStatus
Indicates that an entity’s status is whether it is considered part of the official canon within a given fictional or narrative universe.
-
B.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
C.
storyCanonStatus
Indicates the canonical status of a story relative to an official or primary continuity.
-
D.
hasClosedCanon
Indicates that a body of authoritative texts is considered complete and no additional works can be added to it.
-
E.
canonicalStatusIn
chosen
Indicates that something has a particular canonical or officially recognized status within a specified context or system.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7aaa4f081909e869d2e81b07b91 |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.