Triple
T31847150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大假山 |
E812970
|
entity |
| Predicate | relationToSummerPalace |
P57456
|
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: [大假山, relationToSummerPalace, 构成颐和园重要山石景观节点]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToSummerPalace Context triple: [大假山, relationToSummerPalace, 构成颐和园重要山石景观节点]
-
A.
associatedWithPalace
chosen
Indicates a relationship where an entity has a connection, link, or involvement with a palace, such as through location, function, ownership, or affiliation.
-
B.
positionRelativeToForbiddenCity
Indicates the spatial relationship of an entity’s location with respect to the Forbidden City.
-
C.
hasAncestralPalace
Indicates that an entity possesses or is associated with a palace inherited from its ancestors or historically belonging to its lineage.
-
D.
hasDirectionFromMainPalace
Indicates a directional relationship specifying where something is located or oriented relative to the main palace.
-
E.
palaceLocatedIn
Indicates that a palace is situated within or belongs to a specific geographic or administrative location.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:50 p.m.