Triple
T16919030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 佛香阁 |
E410393
|
entity |
| Predicate | 与万寿山关系 |
P82905
|
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.
与端门关系
Indicates a relationship involving interaction, connection, or association with the Duanmen (端门) gate.
-
B.
associatedWithTempleComplex
chosen
Indicates a relationship in which an entity is connected or related to a specific temple complex, such as by location, function, use, or historical association.
-
C.
positionRelativeToForbiddenCity
Indicates the spatial relationship of an entity’s location with respect to the Forbidden City.
-
D.
皇位継承順位への関係
Indicates the relationship of an entity to the line of succession to the imperial throne, such as its position, eligibility, or connection within that succession order.
-
E.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdec3d0c8190994a0fca335c65d6 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.