Triple
T30155478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 黄鹤楼 |
E766508
|
entity |
| Predicate | 以…闻名 |
P52554
|
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.
bekanntFür
Indicates that one entity is known or recognized for a particular quality, achievement, work, or characteristic associated with another entity.
-
B.
fameFor
chosen
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
oftenRecognizedBy
Indicates that one entity is frequently identified, acknowledged, or noticed by another entity.
-
D.
isInTownKnownFor
Indicates that one entity is located in a town that is notable or distinguished for the other entity.
-
E.
traditionallyKnownFor
Indicates that something is widely and historically recognized or reputed for a particular characteristic, activity, product, or role.
- 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.