Triple
T34654450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rènnas del Castèl |
E889933
|
entity |
| Predicate | hasMythStatus |
P9998
|
FINISHED |
| Object | site of hidden treasure (legend) |
—
|
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: site of hidden treasure (legend) | Statement: [Rènnas del Castèl, hasMythStatus, site of hidden treasure (legend)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythStatus Context triple: [Rènnas del Castèl, hasMythStatus, site of hidden treasure (legend)]
-
A.
hasMythType
chosen
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
B.
hasMythImpact
Indicates that one entity influences, shapes, or contributes to the myths, legends, or mythological narratives associated with another entity.
-
C.
hasMythicMode
Indicates that an entity possesses or supports a special "mythic" difficulty or mode beyond standard levels.
-
D.
hasMythicSetting
Indicates that something is set within a mythic, legendary, or folklore-based world or context.
-
E.
hasMythicMotif
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:04 a.m.