Triple
T26432132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puu Pehe sea stack |
E664537
|
entity |
| Predicate | hasAssociatedLegendCharacter |
P1582
|
FINISHED |
| Object | Pehe |
—
|
NE NERFINISHED |
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: Pehe | Statement: [Puu Pehe sea stack, hasAssociatedLegendCharacter, Pehe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedLegendCharacter Context triple: [Puu Pehe sea stack, hasAssociatedLegendCharacter, Pehe]
-
A.
hasLegendAssociatedWith
chosen
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
B.
hasSiteRelatedToLegend
Indicates that a site is associated with, or thematically connected to, a particular legend or legendary narrative.
-
C.
hasSiblingInLegend
Indicates that one entity is described as the sibling of another entity within a mythological or legendary narrative.
-
D.
inLegendRole
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
-
E.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 11:50 p.m.