Triple
T11612500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine Stock Exchange |
E275416
|
entity |
| Predicate | typeOfSecuritiesTraded |
P40808
|
FINISHED |
| Object | common shares |
—
|
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: common shares | Statement: [Philippine Stock Exchange, typeOfSecuritiesTraded, common shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSecuritiesTraded Context triple: [Philippine Stock Exchange, typeOfSecuritiesTraded, common shares]
-
A.
typeOfSecurityTraded
chosen
Indicates the specific kind or category of security that is being traded in a financial transaction.
-
B.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
C.
isOptionsTraded
Indicates that options contracts based on the referenced entity are actively traded in a financial market.
-
D.
assetClassesTraded
Indicates that an entity trades, deals in, or is involved with specific categories or classes of financial assets.
-
E.
tradesInstrument
Indicates that one party engages in buying, selling, or exchanging a specified financial or tradable instrument.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a043a3c08190a20cbc2ba5a8d218 |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.