Triple
T16737313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmonised Index of Consumer Prices |
E406749
|
entity |
| Predicate | baseConcept |
P64521
|
FINISHED |
| Object | Laspeyres-type index |
—
|
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: Laspeyres-type index | Statement: [Harmonised Index of Consumer Prices, baseConcept, Laspeyres-type index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseConcept Context triple: [Harmonised Index of Consumer Prices, baseConcept, Laspeyres-type index]
-
A.
basingConcept
chosen
Indicates that one concept serves as the foundational basis or underlying rationale for another concept.
-
B.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
C.
primaryConcept
Indicates that one concept is the main or central idea in relation to another concept or context.
-
D.
conceptualType
Indicates that one entity represents the conceptual category, class, or abstract type to which another entity belongs.
-
E.
usesConceptIdentifier
Indicates that one entity refers to or operates with a specific concept by means of its unique identifier.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3b60fc81908cf331448b4b5598 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.