Triple
T1865186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nielsen SoundScan |
E34903
|
entity |
| Predicate | measurementScope |
P14568
|
FINISHED |
| Object | retail sales |
—
|
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: retail sales | Statement: [Nielsen SoundScan, measurementScope, retail sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: measurementScope Context triple: [Nielsen SoundScan, measurementScope, retail sales]
-
A.
measuredBy
Indicates that something’s quantity, extent, or value is determined or expressed using a particular measurement method, instrument, or unit.
-
B.
measurementDependsOn
Indicates that one measurement is derived from, influenced by, or requires another measurement in order to be defined or computed.
-
C.
coverageScope
chosen
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
D.
aimsToMeasure
Indicates that one entity is intended or designed to quantify, assess, or evaluate another entity or property.
-
E.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.