Triple
T5785030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pemon |
E128248
|
entity |
| Predicate | hasMythologyLinkedTo |
P9595
|
FINISHED |
| Object | tepui |
—
|
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: tepui | Statement: [Pemon, hasMythologyLinkedTo, tepui]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythologyLinkedTo Context triple: [Pemon, hasMythologyLinkedTo, tepui]
-
A.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
B.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
C.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
D.
expandsMythologyOf
Indicates that one entity broadens, enriches, or adds new elements to the mythological background or lore associated with another entity.
-
E.
hasMythSource
Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a1af0ec8190a47be1b7e7b5cda7 |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.