Triple
T3725682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord & Taylor |
E81741
|
entity |
| Predicate | notableStoreType |
P51254
|
FINISHED |
| Object | flagship 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: flagship department store | Statement: [Lord & Taylor, notableStoreType, flagship department store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStoreType Context triple: [Lord & Taylor, notableStoreType, flagship department store]
-
A.
notableStore
Indicates that a store is recognized as notable or significant in some context (e.g., historically, culturally, or commercially).
-
B.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
C.
notableBase
Indicates that a particular location serves as a significant or distinguished base or headquarters for an entity.
-
D.
notableLibrary
Indicates that the subject is a library recognized for its significance, prominence, or special importance.
-
E.
notableProjectType
Indicates the type or category of a project for which an entity is particularly well-known or notable.
- F. None of above. chosen
Provenance (4 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf669d48190852aaeef70265404 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc226fffc81909c679b44e611fee6 |
completed | March 8, 2026, 6:38 p.m. |
Created at: March 8, 2026, 3:34 p.m.