Triple
T25782388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KC-45A |
E649324
|
entity |
| Predicate | proposedServiceEntry |
P62980
|
FINISHED |
| Object | United States Air Force |
—
|
NE NERFINISHED |
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: United States Air Force | Statement: [KC-45A, proposedServiceEntry, United States Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedServiceEntry Context triple: [KC-45A, proposedServiceEntry, United States Air Force]
-
A.
serviceEntryWith
Indicates that one entity is associated with or accompanied by a particular service entry in a joint or linked context.
-
B.
serviceEntryInROC
Indicates that a service entry is recorded or included in a Register of Companies (ROC) or similar official registry.
-
C.
plannedService
chosen
Indicates that a service is scheduled or intended to be provided, but has not yet occurred.
-
D.
promotedService
Indicates that one entity actively markets, advertises, or otherwise promotes a particular service to others.
-
E.
serviceEntryContext
Indicates the contextual circumstances or environment in which a particular service entry is created, recorded, or applied.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 5:51 a.m.