Triple
T22472940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air and Space Achievement Medal |
E555551
|
entity |
| Predicate | serviceComponentType |
P117003
|
FINISHED |
| Object | air and space services |
—
|
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: air and space services | Statement: [Air and Space Achievement Medal, serviceComponentType, air and space services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceComponentType Context triple: [Air and Space Achievement Medal, serviceComponentType, air and space services]
-
A.
serviceComponent
Indicates that one entity functions as a component or sub-part within the structure or implementation of a larger service.
-
B.
serviceModuleType
Indicates the type or category of a service module associated with an entity or system.
-
C.
serviceProviderType
Indicates the category or kind of service provider associated with an entity or transaction.
-
D.
serviceBundleType
Indicates the classification or category of a service bundle that specifies what kind of grouped services it represents.
-
E.
servicesType
chosen
Indicates the category or kind of services that one entity provides, uses, or is associated with in relation to 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be2034c81909d1263f2ed114b46 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.