Triple
T48731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Arizona (BB-39) |
E957
|
entity |
| Predicate | fate |
P3146
|
FINISHED |
| Object | sunk during the attack on Pearl Harbor |
—
|
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: sunk during the attack on Pearl Harbor | Statement: [USS Arizona (BB-39), fate, sunk during the attack on Pearl Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fate Context triple: [USS Arizona (BB-39), fate, sunk during the attack on Pearl Harbor]
-
A.
feast
Indicates that an entity participates in or hosts a large, elaborate meal or celebration involving abundant food and communal dining.
-
B.
era
Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
-
C.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
D.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
E.
flag
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abe7cb481908d969e54032f6c75 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24c198e74819088a211001d0b54d4 |
completed | Feb. 28, 2026, 1:59 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.