Triple
T30107051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anzu-bird |
E765160
|
entity |
| Predicate | habitatInMyth |
P168455
|
FINISHED |
| Object | mountains |
—
|
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: mountains | Statement: [Anzu-bird, habitatInMyth, mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: habitatInMyth Context triple: [Anzu-bird, habitatInMyth, mountains]
-
A.
onlyNaturalHabitatOf
Indicates that a given location is the sole natural habitat where a particular species or organism occurs in the wild.
-
B.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
C.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
D.
mythologicalLocation
Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
-
E.
typeOfLocationInMyths
Indicates that a location is classified by the kind of place it is within the context of myths or mythological narratives.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67dbaf34c8190b9ce6f3d9cbad03d |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:09 p.m.