Triple
T35954550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichmann family |
E1039820
|
entity |
| Predicate | businessSetback |
P117819
|
FINISHED |
| Object | Olympia & York bankruptcy in early 1990s |
—
|
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: Olympia & York bankruptcy in early 1990s | Statement: [Reichmann family, businessSetback, Olympia & York bankruptcy in early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessSetback Context triple: [Reichmann family, businessSetback, Olympia & York bankruptcy in early 1990s]
-
A.
sufferedSetback
chosen
Indicates that an entity has experienced a negative event or obstacle that hindered its progress or success.
-
B.
hasSetbackDesign
Indicates that one entity incorporates a design feature that sets it back or away from another reference line, boundary, or structure.
-
C.
businessChallenge
Indicates that an entity faces, presents, or is associated with a problem, obstacle, or difficulty within a business context.
-
D.
business
Indicates that an entity is engaged in commercial or professional activities, such as providing goods or services for profit.
-
E.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.