Triple
T21772204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XF-108 Rapier |
E537460
|
entity |
| Predicate | intendedBaseService |
P145901
|
FINISHED |
| Object | U.S. continental air bases |
—
|
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: U.S. continental air bases | Statement: [XF-108 Rapier, intendedBaseService, U.S. continental air bases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedBaseService Context triple: [XF-108 Rapier, intendedBaseService, U.S. continental air bases]
-
A.
primaryBaseDuringService
Indicates that a particular base or location serves as the main or designated primary base for an entity during a specified period of service.
-
B.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
C.
originatingService
Indicates the service from which an action, request, or piece of data was initially generated or sent.
-
D.
associatedBase
Indicates a relationship where one entity is linked or connected to a corresponding base entity that it depends on or is derived from.
-
E.
introducedForServiceWith
Indicates that one entity was presented or brought to the attention of another entity specifically for the purpose of providing a service.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031af6a488190a2dcebed43d199d4 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:51 p.m.