Triple
T34825828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gowhar-nāmeh |
E1003917
|
entity |
| Predicate | hasMysticalDimension |
P6456
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Gowhar-nāmeh, hasMysticalDimension, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMysticalDimension Context triple: [Gowhar-nāmeh, hasMysticalDimension, true]
-
A.
hasSpiritualDimension
chosen
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
-
B.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
C.
hasMythologicalDomain
Indicates that a mythological figure, deity, or entity is associated with or rules over a particular conceptual or physical domain (such as the sea, war, or the underworld).
-
D.
isMythical
Indicates that the entity is considered mythical, existing only in legend, folklore, or imagination rather than in reality.
-
E.
hasMythicalFigure
Indicates that one entity is associated with, features, or includes a particular mythical or legendary figure.
- 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f77ae15e048190aeb34fa18d7fc9fc |
completed | May 3, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 4 p.m.