Triple
T22541099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Bane |
E557289
|
entity |
| Predicate | createdLukeFrom |
P148590
|
FINISHED |
| Object | human DNA patterns |
—
|
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: human DNA patterns | Statement: [the Bane, createdLukeFrom, human DNA patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdLukeFrom Context triple: [the Bane, createdLukeFrom, human DNA patterns]
-
A.
createdEarlBy
Indicates that an entity was granted or established as an earl by a specific creator or authority.
-
B.
createdDukeBy
Indicates that an entity was made a duke (granted the ducal title or rank) by another specific entity.
-
C.
createdAround
Indicates that something was brought into existence or produced approximately at a particular time or within an imprecise time period.
-
D.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
-
E.
createdInUniverseBy
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
- F. None of above. chosen
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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f3251808190a72b849157854d8d |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:51 p.m.