Triple
T23164057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bradlees |
E578665
|
entity |
| Predicate | notableStoreFormat |
P51254
|
FINISHED |
| Object | discount department store |
—
|
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: discount department store | Statement: [Bradlees, notableStoreFormat, discount department store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStoreFormat Context triple: [Bradlees, notableStoreFormat, discount department store]
-
A.
notableStore
Indicates that a store is recognized as notable or significant in some context (e.g., historically, culturally, or commercially).
-
B.
notableStoreType
chosen
Indicates that a store is particularly recognized or distinguished for being of a specified type (e.g., a notable example of that kind of store).
-
C.
notableFormat
Indicates that something is particularly recognized or distinguished for being in a specific format.
-
D.
notableSave
Indicates that an entity is recognized for having made a particularly significant or memorable save (e.g., in a game, match, or critical situation).
-
E.
notableReader
Indicates that the subject is recognized as a particularly significant or distinguished reader of the object.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2b0414819081f9c2d6b8c88421 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:02 p.m.