Triple
T9741319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foursquare |
E236192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location-based services company |
C27198
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: location-based services company Context triple: [Foursquare, instanceOf, location-based services company]
-
A.
location services solution
A location services solution is a system that collects, processes, and provides geographic position data to enable location-aware features and decision-making for applications and users.
-
B.
transportation services company
A transportation services company is an organization that plans, manages, and operates the movement of people or goods using various modes of transport, such as road, rail, air, or sea, often providing logistics, scheduling, and support services.
-
C.
multinational technology conglomerate
A multinational technology conglomerate is a large corporation that operates across multiple countries and industries, owning and managing diverse technology-focused businesses under a unified corporate structure.
-
D.
telecommunications company
A telecommunications company is an organization that provides communication services such as voice, data, and video transmission over wired or wireless networks to individuals and businesses.
-
E.
cloud services company
A cloud services company provides on-demand computing resources, storage, and software platforms over the internet, enabling organizations to scale and manage their IT infrastructure efficiently without owning physical hardware.
- F. None of above. chosen
Provenance (1 batch)
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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:23 p.m.