Triple
T1419369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GOL Linhas Aéreas Inteligentes |
E31987
|
entity |
| Predicate | mainMarket |
P4848
|
FINISHED |
| Object | Brazilian domestic market |
—
|
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: Brazilian domestic market | Statement: [GOL Linhas Aéreas Inteligentes, mainMarket, Brazilian domestic market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainMarket Context triple: [GOL Linhas Aéreas Inteligentes, mainMarket, Brazilian domestic market]
-
A.
marketType
Indicates the classification or category of market in which an entity operates or a transaction occurs (e.g., retail, wholesale, online).
-
B.
market
Indicates the act of promoting, advertising, or selling a product, service, or idea to potential buyers or target audiences.
-
C.
exportMarket
Indicates that an entity serves as a destination market to which another entity exports goods or services.
-
D.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
E.
hasMajorMarket
chosen
Indicates that an entity has a primary or most significant market in a specified location or segment.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c40631e881909ddf81a2eb84af1c |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.