Triple
T1971837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS O’Brien (DD-415) |
E42817
|
entity |
| Predicate | prewarActivity |
P33336
|
FINISHED |
| Object | Neutrality Patrol in the Atlantic |
—
|
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: Neutrality Patrol in the Atlantic | Statement: [USS O’Brien (DD-415), prewarActivity, Neutrality Patrol in the Atlantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prewarActivity Context triple: [USS O’Brien (DD-415), prewarActivity, Neutrality Patrol in the Atlantic]
-
A.
postwarActivity
Indicates activities, roles, or developments associated with an entity specifically in the period following a war or major conflict.
-
B.
preWarCharacter
Indicates that a character existed or had a particular state or role prior to a specified war or conflict.
-
C.
preWorldWarIIRole
Indicates the role, position, or function an entity held or performed prior to the onset of World War II.
-
D.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
E.
preludeTo
Indicates that one event, action, or state occurs earlier and serves as an introduction or lead-in to another.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f275408190affa93f8cb6a8184 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb16a6db48190af04012e8ed2269f |
completed | March 7, 2026, 5:02 a.m. |
Created at: March 4, 2026, 7:36 p.m.