Triple
T29677254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 安陆市 |
E750848
|
entity |
| Predicate | upgradedToCityLevel |
P80168
|
FINISHED |
| Object | 1980年代 |
—
|
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: 1980年代 | Statement: [安陆市, upgradedToCityLevel, 1980年代]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradedToCityLevel Context triple: [安陆市, upgradedToCityLevel, 1980年代]
-
A.
wasUpgradedToMetropolitanCityIn
Indicates that a city or town was officially elevated in status to a metropolitan city in a specified year or on a specific date.
-
B.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
C.
establishedAsTier
chosen
Indicates that one entity has been formally designated or set to operate at a particular tier or level within a defined hierarchy or system.
-
D.
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.
-
E.
cityLevel
Indicates the administrative or hierarchical rank of a city within a broader regional or national structure.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 7:08 p.m.