Triple
T34521486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic Service Ribbon |
E886289
|
entity |
| Predicate | serviceRequirementType |
P34130
|
FINISHED |
| Object | operational duty |
—
|
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: operational duty | Statement: [Arctic Service Ribbon, serviceRequirementType, operational duty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceRequirementType Context triple: [Arctic Service Ribbon, serviceRequirementType, operational duty]
-
A.
serviceRequirementDetail
Indicates that a specific requirement or condition is associated with the provision or performance of a service.
-
B.
serviceUserRequirement
Indicates that a user has a specific requirement or need that a service is expected to fulfill.
-
C.
typeOfRequirement
Indicates that one requirement is classified as a specific kind or category of another, more general requirement.
-
D.
typicalServiceRequirement
chosen
Indicates that a certain condition, resource, or specification is normally needed or expected for a service to be properly provided or operated.
-
E.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 1, 2026, 2:02 a.m.