Triple
T37464875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deathwing, Mad Aspect |
E931008
|
entity |
| Predicate | canBeGeneratedByDiscover |
P199204
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Deathwing, Mad Aspect, canBeGeneratedByDiscover, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeGeneratedByDiscover Context triple: [Deathwing, Mad Aspect, canBeGeneratedByDiscover, Yes]
-
A.
canGenerateOn
Indicates that one entity has the capability to produce or create another entity specifically on or within a particular medium, platform, or context.
-
B.
hasDiscoveryType
Indicates the specific manner, method, or category by which something was discovered.
-
C.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
D.
canBeConstructedWith
Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
-
E.
canBeCreatedFor
Indicates that one entity is eligible or allowed to be created in association with, or on behalf of, another entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69ff255abca881908ef7635bd2e5af98 |
completed | May 9, 2026, 12:15 p.m. |
Created at: May 3, 2026, 4:17 p.m.