Triple
T26990649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Service Deployment Ribbon |
E679851
|
entity |
| Predicate | appliesToDutyType |
P180929
|
FINISHED |
| Object | sea 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: sea duty | Statement: [Sea Service Deployment Ribbon, appliesToDutyType, sea duty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToDutyType Context triple: [Sea Service Deployment Ribbon, appliesToDutyType, sea duty]
-
A.
hasResponsibilityType
Indicates that an entity bears a specific kind or category of responsibility in relation to another entity or context.
-
B.
appliesToRevenueType
Indicates that a rule, condition, or classification is specifically relevant or applicable to a particular type of revenue.
-
C.
hasDutiesUnder
Indicates that one party is obligated to perform specific responsibilities or fulfill obligations as defined by another party, agreement, or authority.
-
D.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
-
E.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 27, 2026, 6:51 a.m.