Triple
T15363264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASDAQ:SHLD |
E367342
|
entity |
| Predicate | issuerMergerCompletionDate |
P92542
|
FINISHED |
| Object | 2005-03-24 |
—
|
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: 2005-03-24 | Statement: [NASDAQ:SHLD, issuerMergerCompletionDate, 2005-03-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerMergerCompletionDate Context triple: [NASDAQ:SHLD, issuerMergerCompletionDate, 2005-03-24]
-
A.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
B.
mergerPeriod
Indicates the time span during which two or more entities are in the process of merging into a single combined entity.
-
C.
issuedDocumentDate
Indicates the date on which a document was formally created, released, or made officially valid by the issuing party.
-
D.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
E.
timeOfMergerOrAcquisition
chosen
Indicates the specific point in time when a merger or acquisition event occurs between entities.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e479f188190bbbc3dcd73853e02 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca9ab7e88190a9261ef27be665b1 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.