Triple
T35844153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordy Club loyalty program |
E1036162
|
entity |
| Predicate | launchReplaced |
P124454
|
FINISHED |
| Object | Nordstrom Rewards program |
—
|
NE NERFINISHED |
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: Nordstrom Rewards program | Statement: [Nordy Club loyalty program, launchReplaced, Nordstrom Rewards program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchReplaced Context triple: [Nordy Club loyalty program, launchReplaced, Nordstrom Rewards program]
-
A.
relaunch
Indicates restarting or bringing back into operation something that was previously launched, often with changes or improvements.
-
B.
launchAs
chosen
Indicates that one entity initiates or starts another entity in a particular role, mode, or form.
-
C.
launcherReuse
Indicates that a launcher previously used in one mission is used again for another mission.
-
D.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
E.
launchedFeature
Indicates that an entity has released or made a particular feature available for use.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:06 p.m.