Triple
T13089555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swoop |
E310423
|
entity |
| Predicate | servicePolicy |
P57662
|
FINISHED |
| Object | pay-for-what-you-use model |
—
|
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: pay-for-what-you-use model | Statement: [Swoop, servicePolicy, pay-for-what-you-use model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servicePolicy Context triple: [Swoop, servicePolicy, pay-for-what-you-use model]
-
A.
subscriptionPolicy
Indicates the rules, terms, and conditions that govern how a subscription is obtained, used, renewed, or terminated between parties.
-
B.
servicePolicyBeforeCase
Indicates that a service policy is established or applied prior to a specific case or case-related event.
-
C.
supportPolicy
Indicates that one entity endorses, backs, or helps to maintain a particular policy or course of action.
-
D.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
E.
termOfService
chosen
Indicates that one entity defines or specifies the terms of service (rules, conditions, and usage policies) that apply to another entity.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98138a1d481908a139f2f67eb3472 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.