Triple
T26236263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XTAI |
E656179
|
entity |
| Predicate | hasOperatingMarket |
P2714
|
FINISHED |
| Object | Taiwan Stock Exchange |
—
|
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: Taiwan Stock Exchange | Statement: [XTAI, hasOperatingMarket, Taiwan Stock Exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperatingMarket Context triple: [XTAI, hasOperatingMarket, Taiwan Stock Exchange]
-
A.
hasMarket
chosen
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
B.
hasMarketStatus
Indicates the current commercial or trading condition of an entity, such as whether it is active, suspended, listed, or delisted in a market.
-
C.
hasMarketSector
Indicates that an entity operates within, is associated with, or belongs to a particular market sector or industry segment.
-
D.
hasBusinessOperationsIn
Indicates that a business or organization conducts commercial or operational activities within a specified geographic location or jurisdiction.
-
E.
hasRegulatoryMarket
Indicates that an entity is subject to, or operates within, a specific regulatory framework or market oversight regime.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 26, 2026, 9:01 p.m.