Triple
T6172304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loopt |
E137731
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location-based social networking service |
C5716
|
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 social networking service Context triple: [Loopt, instanceOf, location-based social networking service]
-
A.
location services solution
chosen
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.
microblogging service operator
A microblogging service operator is an entity responsible for running, maintaining, and moderating a platform that enables users to post, share, and interact with short-form content in real time.
-
C.
location
A location is a specific place or position in physical or virtual space that can be identified, referenced, and used to describe where entities or events exist or occur.
-
D.
collaborative online platform
A collaborative online platform is a digital environment that enables multiple users to work together in real time or asynchronously by sharing information, coordinating tasks, and communicating through integrated tools and services.
-
E.
health and fitness tracking platform
A health and fitness tracking platform is a digital system that collects, analyzes, and visualizes users’ activity, nutrition, sleep, and biometrics to help them monitor progress and achieve wellness goals.
- F. None of above.
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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:18 p.m.