Triple
T18008827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wireless Emergency Alerts |
E430822
|
entity |
| Predicate | costToSubscribers |
P5902
|
FINISHED |
| Object | free |
—
|
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 | Statement: [Wireless Emergency Alerts, costToSubscribers, free]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costToSubscribers Context triple: [Wireless Emergency Alerts, costToSubscribers, free]
-
A.
costToUser
chosen
Indicates the amount of cost or expense that is borne by, charged to, or incurred by the user.
-
B.
membershipCost
Indicates the monetary amount required to obtain or maintain membership in something.
-
C.
chargesMembershipFee
Indicates that an entity requires another entity to pay a membership fee in order to access its services, benefits, or participation.
-
D.
hasCost
Indicates that one entity requires a specified amount of resources (such as money, time, or effort) to be obtained, used, or maintained by another entity.
-
E.
costModel
Indicates the pricing or cost-structure relationship applied to an entity, defining how its costs are calculated or charged.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51e13788190bebbbdd7340e0982 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.