Triple
T36800671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 崇文门 |
E909312
|
entity |
| Predicate | 方位属性 |
P29149
|
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 the act of determining or establishing the position, location, or placement of one entity relative to a reference point or context.
-
B.
orientationProperty
chosen
Indicates that one entity has a specific spatial or directional orientation in relation to another entity or reference frame.
-
C.
spatialProperty
Indicates a relationship where one entity has a specific spatial characteristic, such as position, size, orientation, or geometric configuration in space, relative to a reference frame or other entities.
-
D.
生态定位
Indicates the ecological role or niche an organism occupies within its environment, including its functional position and interactions in the ecosystem.
-
E.
locationProperty
Indicates that one entity specifies or characterizes a locational attribute or spatial property of another 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.