Triple
T15363025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHLD |
E367336
|
entity |
| Predicate | underlyingCompanyNotableEvent |
P61859
|
FINISHED |
| Object | filed for bankruptcy protection in October 2018 |
—
|
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: filed for bankruptcy protection in October 2018 | Statement: [SHLD, underlyingCompanyNotableEvent, filed for bankruptcy protection in October 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyNotableEvent Context triple: [SHLD, underlyingCompanyNotableEvent, filed for bankruptcy protection in October 2018]
-
A.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
B.
notableCompanyHistory
chosen
Indicates that there exists a significant or historically important relationship or event involving the company and the subject entity.
-
C.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
D.
notableUseEvent
Indicates an event in which something is used in a way that is significant or noteworthy, distinguishing it from ordinary or routine use.
-
E.
hasUnderlyingCompanyWellKnownFor
Indicates that an entity is associated with an underlying company that is widely recognized or notable.
- 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_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.