Triple
T8020862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Section |
E186736
|
entity |
| Predicate | tradingVenueFor |
P6939
|
FINISHED |
| Object | Japanese mid-cap 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: Japanese mid-cap stocks | Statement: [Second Section, tradingVenueFor, Japanese mid-cap stocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingVenueFor Context triple: [Second Section, tradingVenueFor, Japanese mid-cap stocks]
-
A.
hasTradingVenueType
Indicates the specific category or type of trading venue associated with a given trading platform or marketplace.
-
B.
hasTradingVenueCode
Indicates that an entity is associated with a specific trading venue through its designated code.
-
C.
tradedOn
chosen
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
D.
settlementVenue
Indicates the place or institution where a settlement (such as a legal, financial, or dispute resolution agreement) is formally carried out or finalized.
-
E.
tradeSystem
Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8d90488190b57d1e748e272061 |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.