Triple
T20362012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Mark |
E496801
|
entity |
| Predicate | hasBearer |
P458
|
FINISHED |
| Object | Avery |
—
|
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: Avery | Statement: [Dark Mark, hasBearer, Avery]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Avery Context triple: [Dark Mark, hasBearer, Avery]
-
A.
Avery
Avery is a given name most prominently associated with American actor and director Avery Brooks, known for his role as Captain Benjamin Sisko in "Star Trek: Deep Space Nine."
-
B.
Avery
Avery is a publishing imprint known for releasing popular nonfiction books on topics such as health, psychology, and personal growth.
-
C.
Avery
Avery is a surname of English origin borne by various notable individuals across fields such as entertainment, sports, and politics.
-
D.
Avery
chosen
Avery is a Death Eater from the Harry Potter series who was imprisoned in Azkaban for his service to Lord Voldemort.
-
E.
Avery
Avery is the middle name of famed Canadian World War I flying ace Billy Bishop.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6786de5988190827584358c9db147 |
completed | April 20, 2026, 7:03 p.m. |
Created at: April 16, 2026, 11:26 a.m.