Triple
T30916707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zellers |
E787599
|
entity |
| Predicate | leaseSaleValue |
P135624
|
FINISHED |
| Object | about CAD 1.8 billion |
—
|
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: about CAD 1.8 billion | Statement: [Zellers, leaseSaleValue, about CAD 1.8 billion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaseSaleValue Context triple: [Zellers, leaseSaleValue, about CAD 1.8 billion]
-
A.
estateValueUsedFor
Indicates that a specified estate value is applied or allocated for a particular purpose, use, or obligation.
-
B.
leaseOrigin
Indicates that one entity is the original source or starting point from which a lease agreement or leasing arrangement is derived.
-
C.
landAssessmentSystem
Indicates a system or process used to evaluate and determine the value, characteristics, or suitability of land.
-
D.
previousSalePrice
Indicates the price at which an item, asset, or property was sold in its most recent prior transaction before the current one.
-
E.
hasValuation
chosen
Indicates that an entity is assigned or associated with a specific assessed value or worth.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692b251048190ba55b32cac9caf7a |
completed | May 3, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:51 p.m.