Triple
T21910865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air and Space Longevity Service Award |
E541053
|
entity |
| Predicate | serviceTypeRecognized |
P849
|
FINISHED |
| Object | continuous service |
—
|
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: continuous service | Statement: [Air and Space Longevity Service Award, serviceTypeRecognized, continuous service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceTypeRecognized Context triple: [Air and Space Longevity Service Award, serviceTypeRecognized, continuous service]
-
A.
serviceIs
Indicates that one entity functions as a service of a specified type or category in relation to another entity.
-
B.
serviceProviderType
Indicates the category or kind of service provider associated with an entity or transaction.
-
C.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
D.
scopeOfServiceRecognized
Indicates that the extent or range of services provided has been formally acknowledged or accepted.
-
E.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121da36e88190b42b82641ec54a19 |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:40 p.m.