Triple
T30989354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar–Saudi Arabia relations |
E789622
|
entity |
| Predicate | airLinksResumed |
P84124
|
FINISHED |
| Object | January 2021 |
—
|
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: January 2021 | Statement: [Qatar–Saudi Arabia relations, airLinksResumed, January 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airLinksResumed Context triple: [Qatar–Saudi Arabia relations, airLinksResumed, January 2021]
-
A.
airService
chosen
Indicates that an air transportation service (such as flights or air routes) is provided or operates between the related entities.
-
B.
airborneLinkupWith
Indicates a relationship where one entity connects or rendezvous with another while both are in the air or during airborne operations.
-
C.
airTime
Indicates the duration or scheduling time during which something, typically a broadcast or performance, is transmitted or presented.
-
D.
airServiceTransition
Indicates a change or shift in the type, provider, or configuration of air service between locations or entities.
-
E.
supportsAirLink
Indicates that one entity is capable of establishing or maintaining an AirLink wireless connection with another entity.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:56 p.m.