Triple
T11324565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kwang-chou |
E268174
|
entity |
| Predicate | isImportantTradeCenterSince |
P13740
|
FINISHED |
| Object | ancient times |
—
|
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: ancient times | Statement: [Kwang-chou, isImportantTradeCenterSince, ancient times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isImportantTradeCenterSince Context triple: [Kwang-chou, isImportantTradeCenterSince, ancient times]
-
A.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
-
B.
hasMajorHistoricalCentersIn
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
-
C.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
D.
isEconomicCenter
chosen
Indicates that an entity functions as a primary hub for economic activity, such as trade, finance, or industry, within a region or system.
-
E.
isTransportCenterOf
Indicates that a location functions as a primary hub or central node for transportation activities serving another area or network.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e122e48190b3f890de8d561480 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.