Triple
T4331070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wireless Emergency Alerts system |
E96748
|
entity |
| Predicate | usesGPS |
P50216
|
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, usesGPS, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGPS Context triple: [Wireless Emergency Alerts system, usesGPS, true]
-
A.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
B.
locationServices
chosen
Indicates that one entity provides, enables, or manages geographic positioning or place-related functionalities for another entity.
-
C.
hasSatelliteLocation
Indicates that an entity has a secondary or remote location associated with it, such as a branch, satellite office, or auxiliary site.
-
D.
hasNavigationTechnology
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
E.
canProvideDirections
Indicates that one entity is able to give another entity guidance or instructions on how to reach a particular location or navigate a route.
- 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.