Triple
T1305640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RYAAY |
E27869
|
entity |
| Predicate | representsCompanyInMarket |
P2714
|
FINISHED |
| Object | United States equity 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: United States equity market | Statement: [RYAAY, representsCompanyInMarket, United States equity market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsCompanyInMarket Context triple: [RYAAY, representsCompanyInMarket, United States equity market]
-
A.
isMajorCompanyIn
Indicates that a company is a leading or dominant business entity within a specified country, region, or market.
-
B.
memberCompany
Indicates that a company is formally part of, or affiliated as a member with, a larger organization, group, or association.
-
C.
marketedBy
Indicates that one entity is promoted, advertised, or commercially presented to customers by another entity.
-
D.
hasCorporatePresence
Indicates that an organization maintains an official operational or business presence (such as offices, facilities, or legal registration) in a particular location or context.
-
E.
hasMarket
chosen
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c15490a88190872c3d2698a8f9c9 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee9e4a88190b22ab2ee831a23c9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.