Triple
T12601351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yahsat |
E300864
|
entity |
| Predicate | fleet |
P6198
|
FINISHED |
| Object | Al Yah 3 |
E991940
|
NE 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: Al Yah 3 | Statement: [Yahsat, fleet, Al Yah 3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Al Yah 3 Context triple: [Yahsat, fleet, Al Yah 3]
-
A.
Al Yah 3
chosen
Al Yah 3 is a communications satellite providing broadband and telecommunication services, particularly aimed at expanding coverage across Africa and Brazil.
-
B.
Al Yah 2
Al Yah 2 is a communications satellite operated by Yahsat that provides telecommunications and broadband services to regions in the Middle East, Africa, and surrounding areas.
-
C.
Al Yah 4
Al Yah 4 is a communications satellite in the Yahsat fleet, providing advanced broadband and connectivity services to regions within its coverage footprint.
-
D.
Al Yah 5
Al Yah 5 is a communications satellite in the Yahsat fleet providing satellite broadband and related services.
-
E.
Al Yah 1
Al Yah 1 is a communications satellite providing telecommunications and broadband services, primarily covering the Middle East, Africa, and Southwest Asia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954d1f6ac8190ab21ca7bcbc80129 |
completed | April 10, 2026, 7:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f684d8b8d081908f271e75e6472914 |
completed | May 2, 2026, 11:12 p.m. |
Created at: April 9, 2026, 5:09 p.m.