Triple
T16658139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Official Charts |
E404787
|
entity |
| Predicate | dataSourcesInclude |
P71759
|
FINISHED |
| Object | retailers |
—
|
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: retailers | Statement: [Official Charts, dataSourcesInclude, retailers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataSourcesInclude Context triple: [Official Charts, dataSourcesInclude, retailers]
-
A.
sourcesInclude
chosen
Indicates that one entity’s content, data, or information is derived from, references, or incorporates material from another specified source.
-
B.
requiresSources
Indicates that something must be supported, justified, or validated by one or more external sources.
-
C.
dataIntegration
Indicates that data from multiple sources is combined, transformed, and unified into a single, coherent dataset or system.
-
D.
containsSourceRocks
Indicates that a geological unit or area includes rock formations that can generate hydrocarbons (source rocks).
-
E.
outputIncludes
Indicates that the result or product of a process, function, or action contains or incorporates a specified element or component.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfbfd7c819092c92f6c8da07dbd |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.