Triple
T14557267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FedMart |
E341571
|
entity |
| Predicate | relativeToPeers |
P25304
|
FINISHED |
| Object | early American discount chain |
—
|
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: early American discount chain | Statement: [FedMart, relativeToPeers, early American discount chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToPeers Context triple: [FedMart, relativeToPeers, early American discount chain]
-
A.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
B.
peerOf
Indicates that two entities hold equivalent or comparable status, role, or standing within the same context or system.
-
C.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
D.
relativePlaysIn
Indicates that a person has a relative who plays in (is a member of or participates in) a specified team, group, or organization.
-
E.
relativeLevel
chosen
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2f1490881908673f429e5288c86 |
completed | April 14, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.