Triple
T4331090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wireless Emergency Alerts system |
E96748
|
entity |
| Predicate | supportsGeoTargeting |
P21828
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Wireless Emergency Alerts system, supportsGeoTargeting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGeoTargeting Context triple: [Wireless Emergency Alerts system, supportsGeoTargeting, true]
-
A.
supportsRegionBiasing
Indicates that the subject is capable of applying or honoring region-specific preferences or priorities in its behavior or processing.
-
B.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
-
C.
supportsRegionRestriction
chosen
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
-
D.
usesTargetingSystem
Indicates that an entity employs or relies on a specific targeting system to aim at or select a target.
-
E.
hasTargetAudienceRegion
Indicates that something is intended for or directed toward an audience located in a specific geographic region.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514c39748190900e13e70ed8848c |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.