Triple
T32306402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakokku |
E825381
|
entity |
| Predicate | isRegionalTradingHub |
P13740
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pakokku, isRegionalTradingHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalTradingHub Context triple: [Pakokku, isRegionalTradingHub, true]
-
A.
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.
-
B.
isUrbanAndIndustrialHub
Indicates that a place functions as a major center of urban activity and industrial production.
-
C.
hasMajorCityHub
Indicates that an entity contains or is associated with a primary, high-importance city that functions as a central hub for activity, services, or connectivity.
-
D.
isMajorEconomicAreaFor
Indicates that a location or region serves as a primary center of significant economic activity for a specified entity or sector.
-
E.
hasRegionalTrade
Indicates that there is an ongoing or established trade relationship between two regions or territorial entities.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd83c5948190b534ba5d731a11ba |
completed | May 3, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:45 a.m.