Triple
T29210923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puhar |
E740543
|
entity |
| Predicate | tradeLinks |
P11359
|
FINISHED |
| Object | Southeast Asia |
—
|
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: Southeast Asia | Statement: [Puhar, tradeLinks, Southeast Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeLinks Context triple: [Puhar, tradeLinks, Southeast Asia]
-
A.
tradeNetwork
Indicates a relationship where entities are connected through the exchange of goods, services, or resources within an ongoing system of trade.
-
B.
tradeHubWith
Indicates that one entity functions as a central location or node for trading activities in connection with another entity.
-
C.
economicLink
Indicates a relationship where entities are connected through economic interactions, dependencies, or exchanges such as trade, investment, or financial flows.
-
D.
tradingLinks
chosen
Indicates that there are established trade or commercial exchange relationships between the referenced entities.
-
E.
tradeFocus
Indicates a primary emphasis on or specialization in a particular type of trade, transaction, or commercial activity within the relationship or context.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 12:11 p.m.