Triple
T19296529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osaka Securities Exchange |
E482577
|
entity |
| Predicate | listedAssetType |
P15055
|
FINISHED |
| Object | stocks |
—
|
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: stocks | Statement: [Osaka Securities Exchange, listedAssetType, stocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listedAssetType Context triple: [Osaka Securities Exchange, listedAssetType, stocks]
-
A.
assetType
chosen
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
B.
ownsAssetType
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
C.
listingType
Indicates the category or format under which an item, property, or service is offered or advertised (e.g., for sale, for rent, auction, etc.).
-
D.
assetTypeMaintained
Indicates that a particular type or category of asset is kept in proper working condition through maintenance activities.
-
E.
governsAssetType
Indicates that one entity has authority or control over the rules, usage, or management of a particular type or class of asset.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc85e8988190a98bc291121f0153 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.