Triple
T482918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesquite |
E9808
|
entity |
| Predicate | hasRetailNode |
P5259
|
FINISHED |
| Object | regional retail centers along major highways |
—
|
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: regional retail centers along major highways | Statement: [Mesquite, hasRetailNode, regional retail centers along major highways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetailNode Context triple: [Mesquite, hasRetailNode, regional retail centers along major highways]
-
A.
hasRetailFormat
Indicates that one entity operates or is organized according to a particular retail format or store type.
-
B.
hasOnlineCatalog
Indicates that an entity provides a catalog of its items or offerings that is accessible via the internet.
-
C.
isCommercialHubIn
Indicates that a place functions as a primary center of commercial or business activity within a specified larger area or region.
-
D.
dealerNetworkCharacteristic
chosen
Indicates a characteristic or attribute that describes some aspect of a dealer network.
-
E.
hasGiftShop
Indicates that an entity includes or provides access to a gift shop as part of its facilities or services.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0b8fe6081909f8ab87bfda6b2d8 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf321288190b5d560f75782c2cb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.