Triple
T27746875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Decatur (DD-341) |
E702006
|
entity |
| Predicate | primaryRoles |
P110022
|
FINISHED |
| Object | patrol duties |
—
|
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: patrol duties | Statement: [USS Decatur (DD-341), primaryRoles, patrol duties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoles Context triple: [USS Decatur (DD-341), primaryRoles, patrol duties]
-
A.
principalRoleIn
Indicates that an entity holds the primary or leading role in a particular context, activity, or relationship.
-
B.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
C.
primaryAdministrativeRole
Indicates that an entity holds the main or most significant administrative position or function in relation to another entity.
-
D.
primaryRoleOnLine
Indicates that an entity serves as the main or most important role associated with a particular line (such as a transit line, product line, or communication line).
-
E.
currentPrimaryRole
chosen
Indicates the role an entity is presently holding as its main or most important function or position.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: April 27, 2026, 4:16 p.m.