Triple
T26904866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Herndon (DD-198) |
E677223
|
entity |
| Predicate | primaryMissions |
P198075
|
FINISHED |
| Object | patrol 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: patrol duty | Statement: [USS Herndon (DD-198), primaryMissions, patrol duty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMissions Context triple: [USS Herndon (DD-198), primaryMissions, patrol duty]
-
A.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
B.
primaryMissionProgram
Indicates that an entity serves as the main or principal program under which another entity’s mission or primary activity is organized or executed.
-
C.
laterPrimaryMission
Indicates that one mission occurs after another mission in the sequence of primary missions.
-
D.
tertiaryMission
Indicates a relationship where an entity has a third-level or lower-priority mission or objective in addition to its primary and secondary missions.
-
E.
primaryMissionDependency
Indicates that one mission’s success, initiation, or continuation depends directly on the completion or outcome of another mission.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69fec8adaa308190a9a276f8c36f15f0 |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 27, 2026, 5:58 a.m.