Triple
T26371526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 奉化区 |
E660784
|
entity |
| Predicate | administrativelyUpgradedFrom |
P173344
|
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: [奉化区, administrativelyUpgradedFrom, 奉化市]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativelyUpgradedFrom Context triple: [奉化区, administrativelyUpgradedFrom, 奉化市]
-
A.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
B.
upgradedBy
Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
-
C.
upgradesFrom
Indicates that one entity is a newer or improved version that replaces or enhances another entity.
-
D.
upgradedToGroup1From
Indicates that an entity has been elevated or transitioned into group 1 status from another specified source group or category.
-
E.
underwentUpgradeAfter
Indicates that one entity experienced an upgrade or improvement at some point after another specified event or time associated with a second entity.
- F. None of above. chosen
Provenance (4 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 26, 2026, 10:58 p.m.