Triple
T36611403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgulduin |
E903474
|
entity |
| Predicate | waterDescribedAs |
P144915
|
FINISHED |
| Object | corrupted |
—
|
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: corrupted | Statement: [Morgulduin, waterDescribedAs, corrupted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterDescribedAs Context triple: [Morgulduin, waterDescribedAs, corrupted]
-
A.
waterDepiction
Indicates that one entity visually represents or portrays water in some form (e.g., as a subject, element, or feature) in an image or depiction.
-
B.
waterRepresentation
chosen
Indicates how water is depicted, modeled, or symbolized in relation to an entity or context.
-
C.
waterIsKnownFor
Indicates that something is recognized or notable for its association with water, such as its abundance, use, or characteristic relation to water.
-
D.
waterFunction
Indicates that one entity serves a particular role, purpose, or function in relation to water (e.g., how it uses, manages, affects, or interacts with water).
-
E.
surfaceWater
Indicates that one entity consists of or contains surface-level water associated with another entity.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:11 p.m.