Triple
T38589762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaelastrasz the Corrupt |
E932425
|
entity |
| Predicate | mountForm |
P192120
|
FINISHED |
| Object | dragon |
—
|
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: dragon | Statement: [Vaelastrasz the Corrupt, mountForm, dragon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountForm Context triple: [Vaelastrasz the Corrupt, mountForm, dragon]
-
A.
mayForm
Indicates that one entity has the potential or permission to be combined or configured to create, constitute, or result in another entity or structure.
-
B.
nativeForm
Indicates that one entity is the original or native linguistic form of another, such as a word’s form in its source language.
-
C.
formsFusionWith
Indicates that two or more entities combine to create a single, unified entity or structure.
-
D.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
-
E.
enablesForm
Indicates that one entity provides the capability or conditions necessary for a particular form, format, or structured representation of another entity to exist or be used.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:32 p.m.