Triple
T512917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Pennsylvania (BB-38) |
E10644
|
entity |
| Predicate | locationDuringAttackOnPearlHarbor |
P14102
|
FINISHED |
| Object | dry dock at 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: dry dock at Pearl Harbor | Statement: [USS Pennsylvania (BB-38), locationDuringAttackOnPearlHarbor, dry dock at Pearl Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationDuringAttackOnPearlHarbor Context triple: [USS Pennsylvania (BB-38), locationDuringAttackOnPearlHarbor, dry dock at Pearl Harbor]
-
A.
roleAtPearlHarbor
Indicates the specific role, position, or function an entity held in relation to the events at Pearl Harbor.
-
B.
statusDuringPearlHarbor
chosen
Indicates the role, condition, or situation an entity held specifically during the time of the Pearl Harbor attack.
-
C.
dateOfPearlHarborAttackParticipation
Indicates that an entity participated in the attack on Pearl Harbor on December 7, 1941.
-
D.
wasBombedOn
Indicates that a location or target experienced a bombing event at a specific time or date.
-
E.
countryAttacked
Indicates that one country has carried out an attack against another country.
- F. None of above.
Provenance (3 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f232fa688190b08a2fe3f22c7a6e |
completed | Feb. 28, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69a2f013c05481909e6dc87e7b20ebd8 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.