Triple
T8825157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Prices |
E209996
|
entity |
| Predicate | typeOfDataUsed |
P66881
|
FINISHED |
| Object | price series |
—
|
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: price series | Statement: [History of Prices, typeOfDataUsed, price series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDataUsed Context triple: [History of Prices, typeOfDataUsed, price series]
-
A.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
B.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
C.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
D.
typeOfInformation
chosen
Indicates that one entity specifies the category or kind of information that characterizes or describes another entity.
-
E.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc603220508190b64e22dec3ee5ceb |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:46 p.m.