Triple
T11095108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stock Exchange of Thailand |
E262357
|
entity |
| Predicate | tradingCommenced |
P8757
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Stock Exchange of Thailand, tradingCommenced, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingCommenced Context triple: [Stock Exchange of Thailand, tradingCommenced, 1975]
-
A.
tradingSegment
Indicates that one entity operates within, or is associated with, a specific trading segment or market subdivision for transactional activities.
-
B.
actualTrading
Indicates the occurrence of real, executed trading activity between parties, as opposed to planned, simulated, or potential trades.
-
C.
tradingStatus
Indicates the current state or condition of an entity’s ability to be traded or engaged in trading activities.
-
D.
tradedSince
chosen
Indicates that an entity has been actively traded starting from a specified point in time and continuing thereafter.
-
E.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0783e88190aae3d461730c2d70 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.