Triple
T23540391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Fletcher |
E577726
|
entity |
| Predicate | storeStatus |
P152731
|
FINISHED |
| Object | struggling business |
—
|
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: struggling business | Statement: [Mr. Fletcher, storeStatus, struggling business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storeStatus Context triple: [Mr. Fletcher, storeStatus, struggling business]
-
A.
storesPackageStatusIn
Indicates that an entity records or maintains the status information of a package within a particular storage location or system.
-
B.
store
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
C.
listedStatus
Indicates that an entity has an official listing designation or status within a defined registry, catalog, or classification system.
-
D.
distributionStatus
Indicates the current state or phase of how something is being distributed, such as whether distribution is planned, in progress, completed, or halted.
-
E.
storefront
Indicates the physical or virtual front-facing location where a business presents and offers its goods or services to customers.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1a66b88190811b38523ea606fe |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:10 p.m.