Triple
T575416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Play Store |
E13751
|
entity |
| Predicate | supportsBusinessModel |
P6233
|
FINISHED |
| Object | free apps |
—
|
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: free apps | Statement: [Google Play Store, supportsBusinessModel, free apps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBusinessModel Context triple: [Google Play Store, supportsBusinessModel, free apps]
-
A.
usesBusinessModel
chosen
Indicates that one entity operates according to, or applies in practice, the business model defined or provided by another entity.
-
B.
operatingModel
Indicates how an organization structures and manages its processes, resources, and governance to deliver its products or services.
-
C.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
D.
supportsVentureType
Indicates that an entity provides backing, resources, or compatibility for a specified type or category of venture.
-
E.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b67395c8190a8046ff7debe9d1f |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c4969c819080375d08f9eec50c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.