Triple
T5261501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BA:US |
E118833
|
entity |
| Predicate | hasMarketDataFields |
P28893
|
FINISHED |
| Object | last price |
—
|
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: last price | Statement: [BA:US, hasMarketDataFields, last price]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketDataFields Context triple: [BA:US, hasMarketDataFields, last price]
-
A.
hasMarketData
Indicates that an entity possesses or is associated with relevant market-related information or statistics.
-
B.
hasMarketDataFeed
Indicates that an entity provides, supports, or is associated with a stream of market-related data (such as prices, quotes, or trading information) to another entity or system.
-
C.
hasDataFields
chosen
Indicates that an entity possesses or is associated with specific data fields or attributes.
-
D.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
-
E.
hasMarketIndex
Indicates that an entity is associated with, or tracked by, a specific market index.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd0c5f48190a1be89314c59f96b |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.