Triple
T36054487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Potter's wand |
E1042905
|
entity |
| Predicate | sharesPhoenixFeatherSourceWith |
P178253
|
FINISHED |
| Object | Lord Voldemort's wand |
—
|
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: Lord Voldemort's wand | Statement: [Harry Potter's wand, sharesPhoenixFeatherSourceWith, Lord Voldemort's wand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPhoenixFeatherSourceWith Context triple: [Harry Potter's wand, sharesPhoenixFeatherSourceWith, Lord Voldemort's wand]
-
A.
phoenixFeatherFrom
Indicates that something is made from, contains, or originates from the feather of a phoenix.
-
B.
sharesFoundationWith
chosen
Indicates that two entities are based on, derived from, or built upon the same underlying foundation, origin, or core source.
-
C.
sharesFeatureWith
Indicates that two entities have at least one common attribute, property, or characteristic in common.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
sharesMascotWith
Indicates that two entities have the same mascot, symbol, or representative figure.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:08 p.m.