Triple
T8826112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERJ |
E210018
|
entity |
| Predicate | isForeignListingFor |
P84840
|
FINISHED |
| Object | Embraer S.A. common shares |
—
|
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: Embraer S.A. common shares | Statement: [ERJ, isForeignListingFor, Embraer S.A. common shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isForeignListingFor Context triple: [ERJ, isForeignListingFor, Embraer S.A. common shares]
-
A.
isListing
Indicates that an entity functions as a listing, typically representing an item, service, or offering that is being presented, advertised, or made available.
-
B.
isListedEntityThrough
Indicates that one entity is recognized or recorded as a listed entity by means of, or via the involvement of, another entity or mechanism.
-
C.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
D.
countryOfListing
Indicates that a company or financial instrument is officially listed and traded in the specified country’s market or exchange.
-
E.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc60332d208190972a8b03fbd760ee |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:46 p.m.