Triple
T36592224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fomento Económico Mexicano, S.A.B. de C.V. |
E902700
|
entity |
| Predicate | hasMexicanTicker |
P199994
|
FINISHED |
| Object | FEMSA |
—
|
NE NERFINISHED |
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: FEMSA | Statement: [Fomento Económico Mexicano, S.A.B. de C.V., hasMexicanTicker, FEMSA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMexicanTicker Context triple: [Fomento Económico Mexicano, S.A.B. de C.V., hasMexicanTicker, FEMSA]
-
A.
hasTickerCountryCode
Indicates that a financial instrument’s ticker symbol is associated with a specific country code.
-
B.
hasExchangeTicker
Indicates that an entity is identified or listed under a specific ticker symbol on a particular financial exchange.
-
C.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
D.
hasUnderlyingExchangeTicker
Indicates that one financial instrument is based on, or derives its value from, another instrument identified by a specific exchange ticker.
-
E.
hasMarketMakers
Indicates that an entity is associated with one or more market makers who provide liquidity or facilitate trading for it.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
| PDg | Predicate description generation | batch_69ff691e86d0819099fdb5eca5a95632 |
completed | May 9, 2026, 5:04 p.m. |
Created at: May 3, 2026, 4:11 p.m.