Triple
T9028051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Developer Transition Kit (Intel) |
E216095
|
entity |
| Predicate | priceModel |
P8244
|
FINISHED |
| Object | rental fee for limited period |
—
|
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: rental fee for limited period | Statement: [Developer Transition Kit (Intel), priceModel, rental fee for limited period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priceModel Context triple: [Developer Transition Kit (Intel), priceModel, rental fee for limited period]
-
A.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
-
B.
priceCategory
Indicates the classification of an item or service based on its price level or cost range.
-
C.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
D.
pricingStrategy
chosen
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
-
E.
productPricing
Indicates the pricing details or cost structure assigned to a specific product.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7fcb308190af90d6be8700e498 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.