Triple
T24761706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deathly Hallows |
E619462
|
entity |
| Predicate | fictional entity |
P84710
|
FINISHED |
| Object | Harry Potter universe |
—
|
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: Harry Potter universe | Statement: [Deathly Hallows, fictional entity, Harry Potter universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictional entity Context triple: [Deathly Hallows, fictional entity, Harry Potter universe]
-
A.
fictionalEntityType
Indicates that the subject is classified as a particular type or category of fictional entity within a narrative or imaginary context.
-
B.
fictionalObject
chosen
Indicates that one entity is a fictional or imaginary object in relation to another entity.
-
C.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
D.
fictionalSon
Indicates that one entity is portrayed as the son of another entity within a fictional or narrative context.
-
E.
fictionalStandInFor
Indicates that one entity serves as a fictional or symbolic substitute representing another real or implied 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:27 a.m.