Triple
T30155518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 黄鹤楼 |
E766508
|
entity |
| Predicate | 相关传说 |
P102058
|
FINISHED |
| Object | 仙人乘黄鹤飞去的传说 |
—
|
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: 仙人乘黄鹤飞去的传说 | Statement: [黄鹤楼, 相关传说, 仙人乘黄鹤飞去的传说]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 相关传说 Context triple: [黄鹤楼, 相关传说, 仙人乘黄鹤飞去的传说]
-
A.
associatedTale
chosen
Indicates that one entity is linked or connected to a particular tale, story, or narrative.
-
B.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
C.
folkloreFunction
Indicates that something serves a role, purpose, or function within a body of folklore, such as myths, legends, or traditional narratives.
-
D.
hasTraditionalStory
Indicates that one entity possesses, is associated with, or is the source or subject of a traditional story related to the other entity.
-
E.
mythologicalEvent
Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed72fb08190955d6bfd90dd3b8e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.