Triple
T5989591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS San Francisco (CA-38) |
E133310
|
entity |
| Predicate | survivedAttackOnPearlHarbor |
P48637
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [USS San Francisco (CA-38), survivedAttackOnPearlHarbor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivedAttackOnPearlHarbor Context triple: [USS San Francisco (CA-38), survivedAttackOnPearlHarbor, yes]
-
A.
dateOfPearlHarborAttackParticipation
Indicates that an entity participated in the attack on Pearl Harbor on December 7, 1941.
-
B.
survivedSecondSinoJapaneseWar
Indicates that the subject continued to live through and beyond the duration of the Second Sino-Japanese War.
-
C.
wasBombedDuring
Indicates that an entity was subjected to a bombing attack during a specified event or time period.
-
D.
wasBombardedDuring
Indicates that an entity was subjected to a bombardment (e.g., shelling, bombing, or heavy attack) during a specified event or time period.
-
E.
survivedConflict
chosen
Indicates that an entity continued to live or exist after experiencing and enduring a specific conflict or violent event.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc76fd481908cc3f327e532a1a6 |
completed | March 22, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.