Triple
T35124793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sa Kaeo |
E1014269
|
entity |
| Predicate | borderTradeImportance |
P195638
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Sa Kaeo, borderTradeImportance, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTradeImportance Context triple: [Sa Kaeo, borderTradeImportance, high]
-
A.
portImportance
Indicates the relative significance or strategic value of a port within a given context (such as trade, logistics, or transportation networks).
-
B.
borderTradeType
Indicates the specific category or nature of trade that occurs across a border between two regions or countries.
-
C.
strategicImportanceDueTo
Indicates that one entity possesses strategic significance specifically as a result of its connection, characteristics, or influence related to another entity.
-
D.
borderTradeStatus
chosen
Indicates the current condition or level of activity of trade occurring across a shared border between two regions or countries.
-
E.
shippingLaneImportance
Indicates the degree to which a particular shipping lane is considered significant or critical relative to other possible routes.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
Created at: May 3, 2026, 4:01 p.m.