Triple
T475344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JBLU |
E9048
|
entity |
| Predicate | quoteSource |
P409
|
FINISHED |
| Object | NASDAQ real-time price (for eligible feeds) |
—
|
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: NASDAQ real-time price (for eligible feeds) | Statement: [JBLU, quoteSource, NASDAQ real-time price (for eligible feeds)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quoteSource Context triple: [JBLU, quoteSource, NASDAQ real-time price (for eligible feeds)]
-
A.
notableQuote
Indicates that one entity is a significant or well-known quotation attributed to, recorded by, or strongly associated with another entity.
-
B.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
C.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
D.
citation
Indicates that one entity references, quotes, or otherwise acknowledges another entity as a source of information or authority.
-
E.
citationBy
Indicates that one work is cited or referenced by another work.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03b5e5081908ee3dba9d19a6871 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edeed31881908cf43beed410572d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.