Triple
T1852916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Mustin (DD-413) |
E41635
|
entity |
| Predicate | serviceHistory |
P33594
|
FINISHED |
| Object | saw extensive action in World War II |
—
|
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: saw extensive action in World War II | Statement: [USS Mustin (DD-413), serviceHistory, saw extensive action in World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceHistory Context triple: [USS Mustin (DD-413), serviceHistory, saw extensive action in World War II]
-
A.
ownershipHistory
Indicates the sequence of past and present owners associated with an entity over time.
-
B.
suspensionHistory
Indicates a record of past instances in which an entity was suspended, including when and possibly why those suspensions occurred.
-
C.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
D.
hasTransportHistory
Indicates that there exists a record or sequence of past transportation-related events or movements associated with an entity.
-
E.
hasTransportHistoryAs
Indicates that an entity has a record or log of being transported, characterized or classified in a specific way.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69abb22f36f08190abf5e295ddf310d7 |
completed | March 7, 2026, 5:05 a.m. |
Created at: March 4, 2026, 7:33 p.m.