Triple
T31022462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XHKG |
E790485
|
entity |
| Predicate | isTradingVenueFor |
P172854
|
FINISHED |
| Object | equities |
—
|
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: equities | Statement: [XHKG, isTradingVenueFor, equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTradingVenueFor Context triple: [XHKG, isTradingVenueFor, equities]
-
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.
usesTradingVenues
Indicates that one entity conducts trading activities through, or executes trades on, specific trading venues associated with another entity.
-
D.
isElectronicTradingVenue
Indicates that one entity functions as a platform or venue where trading activities are conducted electronically rather than through traditional physical or manual means.
-
E.
identifiesTradingVenue
Indicates that one entity specifies or designates the trading venue associated with another entity or transaction.
- F. None of above. chosen
Provenance (4 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 29, 2026, 8:58 p.m.