Triple
T36635899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SET50 Index |
E904461
|
entity |
| Predicate | componentListingVenue |
P41818
|
FINISHED |
| Object | Stock Exchange of Thailand |
—
|
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: Stock Exchange of Thailand | Statement: [SET50 Index, componentListingVenue, Stock Exchange of Thailand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentListingVenue Context triple: [SET50 Index, componentListingVenue, Stock Exchange of Thailand]
-
A.
hasListingVenue
chosen
Indicates that an item, event, or offering is associated with the specific venue where it is listed or made available.
-
B.
coVenueWith
Indicates that two events or activities take place at the same venue or location.
-
C.
featuresVenue
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
-
D.
hasListingVenueCity
Indicates that an entity’s listing is associated with a specific city as its venue location.
-
E.
homeVenueIncludes
Indicates that a specified venue is part of, contained within, or used as a home location by another entity.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:11 p.m.