Triple
T36800665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 崇文门 |
E909312
|
entity |
| Predicate | 邻近建筑 |
P77342
|
FINISHED |
| Object | 新世界商场 |
—
|
NE NERFINISHED |
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.
hasNeighboringBuilding
chosen
Indicates that one building is located adjacent to or directly next to another building.
-
B.
adjacentBuildingFunction
Indicates that two buildings located next to each other have a specified functional relationship or usage connection.
-
C.
attachedBuilding
Indicates that one building is physically connected to or joined with another building as part of the same structural complex.
-
D.
architectOfSurroundingBuildings
Indicates that one entity is the architect responsible for designing the buildings that surround or are adjacent to another specified entity.
-
E.
hasMainBuildingNear
Indicates that the primary or central building associated with an entity is located in close physical proximity to another specified entity or place.
- 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.