Triple
T5354117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shungnak |
E102647
|
entity |
| Predicate | communicationAccess |
P2798
|
FINISHED |
| Object | satellite-based internet |
—
|
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: satellite-based internet | Statement: [Shungnak, communicationAccess, satellite-based internet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationAccess Context triple: [Shungnak, communicationAccess, satellite-based internet]
-
A.
communicationFunction
Indicates that one entity serves a communicative role or purpose in relation to another, such as conveying, mediating, or facilitating the exchange of information.
-
B.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
C.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
-
D.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
E.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86149774819084049a8785e3f2e0 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.