Triple
T7087487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WFM (former) |
E165113
|
entity |
| Predicate | postAcquisitionStatus |
P74456
|
FINISHED |
| Object | no longer trades under this symbol |
—
|
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: no longer trades under this symbol | Statement: [WFM (former), postAcquisitionStatus, no longer trades under this symbol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postAcquisitionStatus Context triple: [WFM (former), postAcquisitionStatus, no longer trades under this symbol]
-
A.
acquisitionStatus
Indicates the current state or outcome of an acquisition process between entities (e.g., pending, completed, failed, or canceled).
-
B.
submissionStatus
Indicates the current state or phase of a submitted item within a review or processing workflow.
-
C.
afterAcquisitionName
Indicates that the object entity represents the name used by a company or organization after it has been acquired.
-
D.
acquisitionResultedIn
Indicates that an acquisition event led to a particular outcome, state, or consequence for the involved entities.
-
E.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
- F. None of above. chosen
Provenance (4 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e513d9b08190a8a8d213c2264ce4 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e24af9ac8190b24eee206ba8be36 |
completed | March 27, 2026, 8:02 p.m. |
Created at: March 27, 2026, 2:41 p.m.