Triple
T20840099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenandoah, Texas |
E513071
|
entity |
| Predicate | hasRetailCenters |
P142047
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shenandoah, Texas, hasRetailCenters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetailCenters Context triple: [Shenandoah, Texas, hasRetailCenters, yes]
-
A.
hasRetailStores
Indicates that an entity operates or possesses one or more physical retail store locations.
-
B.
hasRetailPresenceIn
Indicates that an entity conducts retail operations or maintains a retail outlet, store, or sales presence within a specified location.
-
C.
hasRetailNetwork
Indicates that an entity operates or is associated with a system of retail outlets or distribution channels through which products or services are sold.
-
D.
hasRetailBoutiquesIn
Indicates that an entity operates or maintains retail boutiques located within a specified place or region.
-
E.
hasDistributionCenters
Indicates that one entity maintains or operates one or more distribution centers associated with another entity or area.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34a60848190b33078172675f8d7 |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:43 p.m.