Triple
T33836958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 安定门 |
E867258
|
entity |
| Predicate | 地理属性 |
P12436
|
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 characteristics or qualities of a location that define its situational conditions or advantages in relation to its surroundings.
-
B.
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.
-
C.
hasGeographyCharacteristic
chosen
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
D.
geographicalNature
Indicates the natural geographic characteristics or physical landscape type associated with a place or region.
-
E.
geographicalStructure
Indicates a relationship where one entity is a physical geographic feature or formation that characterizes or shapes the spatial nature of another entity or area.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7002f38308190af948b97a35a5b09 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.