Triple
T8906463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 外滩 |
E212071
|
entity |
| Predicate | 建筑风格特征 |
P52857
|
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.
architecturalStyle
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
B.
architecturalStyleIncludes
Indicates that a structure, building, or design incorporates or exemplifies a particular architectural style as one of its defining characteristics.
-
C.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
D.
hasReligiousBuildingStyle
Indicates that one entity (typically a building) exhibits or is characterized by the architectural style associated with a particular religion or religious tradition.
-
E.
hasBuildingStyleInSurroundings
chosen
Indicates that an entity is surrounded by or located in an area characterized by a particular building style.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc64c51d6c819098dc33a480dfd462 |
completed | April 1, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.