Triple
T7422495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Target Corporation |
E171282
|
entity |
| Predicate | openedFirstTargetStore |
P617
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [Target Corporation, openedFirstTargetStore, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedFirstTargetStore Context triple: [Target Corporation, openedFirstTargetStore, 1962]
-
A.
openedFirstHypermarket
Indicates that the subject entity was the first to open a hypermarket for the object entity or within the context specified.
-
B.
openedFirstBoutiqueIn
Indicates that an entity established its first boutique or retail store in a specified location.
-
C.
openedIn
chosen
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
D.
openedFirstLine
Indicates that one entity initiated the opening of something (e.g., a file, document, or interface) before any other entity did, being the first to perform the opening action.
-
E.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ed29ec8190804564185fe20797 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.