Triple
T13823203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 中和殿 |
E332185
|
entity |
| Predicate | positionRelativeTo太和殿 |
P59923
|
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: [中和殿, positionRelativeTo太和殿, 位于太和殿之后]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeTo太和殿 Context triple: [中和殿, positionRelativeTo太和殿, 位于太和殿之后]
-
A.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
B.
positionRelativeToBuilding
chosen
Indicates the spatial relationship of an entity’s location with respect to a specific building (e.g., in front of, behind, adjacent to, on top of).
-
C.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
E.
positionRelativeToTower
Indicates the spatial relationship or placement of an entity with respect to a specified tower.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0284428081908043c55caeefb833 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.