Triple
T36592362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sociedad Anónima Bursátil de Capital Variable |
E902704
|
entity |
| Predicate | typicalListingVenue |
P25526
|
FINISHED |
| Object | Mexican Stock Exchange |
E229111
|
NE 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: Mexican Stock Exchange | Statement: [Sociedad Anónima Bursátil de Capital Variable, typicalListingVenue, Mexican Stock Exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalListingVenue Context triple: [Sociedad Anónima Bursátil de Capital Variable, typicalListingVenue, Mexican Stock Exchange]
-
A.
hasListingVenue
Indicates that an item, event, or offering is associated with the specific venue where it is listed or made available.
-
B.
typicalVenues
chosen
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
C.
featuresVenue
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
-
D.
hasListingVenueCity
Indicates that an entity’s listing is associated with a specific city as its venue location.
-
E.
coVenueWith
Indicates that two events or activities take place at the same venue or location.
- F. None of above.
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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a380efb1c81908ee75cfa0224c654 |
completed | June 23, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.