Triple
T10034929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 黄冈市 |
E204941
|
entity |
| Predicate | 历史文化 |
P45682
|
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.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
B.
historicalDiscipline
Indicates that one entity is a field or branch of academic study within the broader domain of history in relation to another entity.
-
C.
culturalHeritageOf
chosen
Indicates that something serves as the cultural heritage belonging to, originating from, or strongly associated with a particular entity or group.
-
D.
otherHistoricSee
Indicates that an entity is associated with or linked to another historically significant site, event, or point of interest that can be seen or visited.
-
E.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce4a515c8190baec86d924623b12 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.