Triple
T13914737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 交泰殿 |
E334590
|
entity |
| Predicate | positionInAxis |
P94368
|
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: [交泰殿, positionInAxis, 紫禁城中轴线]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInAxis Context triple: [交泰殿, positionInAxis, 紫禁城中轴线]
-
A.
positionInFrame
Indicates the spatial location or coordinates of an entity within a specific frame or reference image.
-
B.
positionAt
Indicates that one entity is located at, or occupies, a specific spatial position relative to another entity or reference frame.
-
C.
isOnAxis
chosen
Indicates that one entity lies directly along a specified axis or reference line defined by another entity or coordinate system.
-
D.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
coordinateAxis
Indicates that one entity serves as a reference axis or directional basis for positioning, measuring, or orienting another entity in a coordinate system.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27260ae08190be45b4b15898e365 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.