Triple
T16058269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Hangleton graveyard |
E389537
|
entity |
| Predicate | connectedObject |
P37306
|
FINISHED |
| Object | Voldemort’s wand |
—
|
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: Voldemort’s wand | Statement: [Little Hangleton graveyard, connectedObject, Voldemort’s wand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedObject Context triple: [Little Hangleton graveyard, connectedObject, Voldemort’s wand]
-
A.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
B.
connectedToEvent
Indicates that an entity has a direct association or linkage with a specific event.
-
C.
relatedDevice
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
-
D.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.