Triple
T1256408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horseshoe |
E12402
|
entity |
| Predicate | hasCustomerSegment |
P809
|
FINISHED |
| Object | tourists |
—
|
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: tourists | Statement: [Horseshoe, hasCustomerSegment, tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerSegment Context triple: [Horseshoe, hasCustomerSegment, tourists]
-
A.
brandSegment
Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
-
B.
customerType
chosen
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
C.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
D.
operatesInSegment
Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
-
E.
hasExpressSegments
Indicates that a route, service, or path includes segments that are designated as express, skipping certain intermediate stops or steps.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfa726548190911b4022dc1be3c3 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.