Triple
T8903765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 蛇山 |
E211994
|
entity |
| Predicate | 知名原因 |
P55574
|
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.
hasPopularityReason
chosen
Indicates that there is a specific reason or factor explaining why something is popular.
-
B.
knownPrimarilyThrough
Indicates that one entity is chiefly recognized, identified, or made familiar to others by means of another entity (such as a work, role, medium, or context).
-
C.
hasNotablePublicityReason
Indicates that an entity is associated with a specific reason or event that has led to notable public attention or publicity.
-
D.
causeOfReputation
Indicates that one entity is the reason or source for another entity’s reputation.
-
E.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc64c2509881908fb692522d348e96 |
completed | April 1, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.