Triple
T4060379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 颐和园 |
E86196
|
entity |
| Predicate | 重建原因 |
P50914
|
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.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
B.
recreated
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
-
C.
reasonForNewBuilding
chosen
Indicates the underlying cause, motivation, or justification for constructing a new building.
-
D.
rebuiltUnder
Indicates that an entity was reconstructed or restored while being subject to the authority, control, or governance of another entity.
-
E.
reconstructionFor
Indicates that one entity serves as a reconstruction, restoration, or rebuilt version 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.