Triple
T6125405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-band |
E136582
|
entity |
| Predicate | ITURegion |
P68290
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [S-band, ITURegion, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ITURegion Context triple: [S-band, ITURegion, global]
-
A.
ISORegion
Indicates a standardized geographic or administrative region as defined by an ISO (International Organization for Standardization) code.
-
B.
europeanRegion
Indicates that an entity is located in, associated with, or classified as part of a region within Europe.
-
C.
countryRegion
Indicates that a country is located within, or belongs to, a specific geographic or administrative region.
-
D.
marketRegion
Indicates the geographic or demographic area in which a product, service, or entity is actively marketed or targeted.
-
E.
worldRegion
Indicates that one entity is a geographic region that encompasses, contains, or is associated with the other entity within the world.
- F. None of above. chosen
Provenance (4 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c2791948190ba33458edfd1ebe8 |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:14 p.m.