Triple
T6581486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P/Case-Shiller Home Price Indices |
E157305
|
entity |
| Predicate | reportingLag |
P45126
|
FINISHED |
| Object | approximately two months |
—
|
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: approximately two months | Statement: [S&P/Case-Shiller Home Price Indices, reportingLag, approximately two months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportingLag Context triple: [S&P/Case-Shiller Home Price Indices, reportingLag, approximately two months]
-
A.
communicationLatency
chosen
Indicates the time delay between when a communication is sent by one entity and when it is received or processed by another.
-
B.
resultsReportedAs
Indicates that the outcomes or findings of an activity, process, or evaluation are communicated or documented in a specified form, format, or medium.
-
C.
scoreReportedTo
Indicates that a score or result has been communicated or submitted from one party to another.
-
D.
requiresReportFrom
Indicates that one entity is obligated to obtain or receive a report from another entity.
-
E.
requiresReportTo
Indicates that one entity is obligated to submit or provide a report to another entity.
- 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_69c6882b3a108190b3a9eb343ae4162c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:54 p.m.