Triple
T23200303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penneys |
E579987
|
entity |
| Predicate | hasAlternativeBrandName |
P51253
|
FINISHED |
| Object | Primark |
—
|
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: Primark | Statement: [Penneys, hasAlternativeBrandName, Primark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeBrandName Context triple: [Penneys, hasAlternativeBrandName, Primark]
-
A.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
B.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
C.
hasAlternativeNameOfOrder
Indicates that one entity is an alternative or variant name used to refer to the same order as the other entity.
-
D.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
-
E.
brandNameVariant
chosen
Indicates that one brand name is an alternative or variant form of another brand name, such as a spelling, regional, or stylistic variation.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f19078f28c8190973f1bd6f2bceb5a |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:06 p.m.