Triple
T36800673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 崇文门 |
E909312
|
entity |
| Predicate | 历史价值 |
P4345
|
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.
heritageValue
Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
-
B.
historicalMaterial
Indicates that something serves as a source or document providing information or evidence about past events or conditions.
-
C.
hasCulturalAndHistoricalSignificance
Indicates that something possesses notable importance or influence within a culture and/or historical context, often due to its impact, symbolism, or role in significant events or traditions.
-
D.
hasHistoricalSignificance
chosen
Indicates that something possesses notable importance or influence within a historical context or period.
-
E.
historicEconomicImportance
Indicates that an entity has played a significant role in economic activity or development during a past period of historical relevance.
- 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.