Triple
T21718495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Maddox (DD-731) |
E536091
|
entity |
| Predicate | missionDuringIncident |
P145080
|
FINISHED |
| Object | signals intelligence patrol |
—
|
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: signals intelligence patrol | Statement: [USS Maddox (DD-731), missionDuringIncident, signals intelligence patrol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionDuringIncident Context triple: [USS Maddox (DD-731), missionDuringIncident, signals intelligence patrol]
-
A.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
-
B.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
C.
missionCadence
Indicates the frequency or regular interval at which missions are planned, launched, or conducted.
-
D.
missionField
Indicates a relationship where an entity’s work, activity, or purpose is directed toward a particular area, domain, or target context as its mission focus.
-
E.
commandedMission
Indicates that one entity served as the commanding leader or officer in charge of a particular mission carried out by another entity.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96cc58081908dda09819041b888 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:47 p.m.