Triple

T15833890
Position Surface form Disambiguated ID Type / Status
Subject Adam Neumann E383936 entity
Predicate stepDownReason P24494 FINISHED
Object pressure from investors following failed IPO attempt 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: pressure from investors following failed IPO attempt | Statement: [Adam Neumann, stepDownReason, pressure from investors following failed IPO attempt]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: stepDownReason
Context triple: [Adam Neumann, stepDownReason, pressure from investors following failed IPO attempt]
  • A. statedReason chosen
    Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
  • B. retreatCause
    Indicates that one event, condition, or factor serves as the reason or trigger for a retreat by an entity.
  • C. stabilityReason
    Indicates the factor, condition, or cause that accounts for why something remains stable or unchanged.
  • D. designationReason
    Indicates the reason or justification for assigning a particular designation or status to an entity.
  • E. suspensionReason
    Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
  • 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e11e6670d48190a456581dd951f168 completed April 16, 2026, 5:37 p.m.
PD Predicate disambiguation batch_69e005418f588190824d91ff7974dada completed April 15, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:49 a.m.