Triple
T36054500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Potter's wand |
E1042905
|
entity |
| Predicate | firstChosenOwner |
P153898
|
FINISHED |
| Object | Harry Potter |
E115634
|
NE 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: Harry Potter | Statement: [Harry Potter's wand, firstChosenOwner, Harry Potter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstChosenOwner Context triple: [Harry Potter's wand, firstChosenOwner, Harry Potter]
-
A.
initialOwner
Indicates the entity that originally possessed, controlled, or owned another entity before any subsequent transfers or changes in ownership.
-
B.
primaryOwner
Indicates that one entity is the main or principal owner of another entity, having the highest level of ownership or control among all possible owners.
-
C.
first_holder
chosen
Indicates that the subject is the earliest or original holder or possessor of the specified object, title, or right.
-
D.
firstOwnerSpecies
Indicates that the subject is the species of the entity that originally owned or possessed the object.
-
E.
firstAcquiredBy
Indicates the entity that initially obtained, purchased, or took ownership of something for the first time.
- F. None of above.
Provenance (4 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_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a390d3444d881908838780fe6886b34 |
completed | June 22, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.