Triple
T5989590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS San Francisco (CA-38) |
E133310
|
entity |
| Predicate | statusOn7December1941 |
P14102
|
FINISHED |
| Object | undergoing overhaul 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: undergoing overhaul at Pearl Harbor | Statement: [USS San Francisco (CA-38), statusOn7December1941, undergoing overhaul at Pearl Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOn7December1941 Context triple: [USS San Francisco (CA-38), statusOn7December1941, undergoing overhaul at Pearl Harbor]
-
A.
statusAfter1941
Indicates the condition or state of an entity as it existed after the year 1941.
-
B.
statusDuringPearlHarbor
chosen
Indicates the role, condition, or situation an entity held specifically during the time of the Pearl Harbor attack.
-
C.
dateOfKamikazeAttack
Indicates the specific calendar date on which a kamikaze attack took place.
-
D.
statusIn1945
Indicates the condition, role, or classification an entity had specifically during the year 1945.
-
E.
dateOfPearlHarborAttack
Indicates the specific calendar date on which the Pearl Harbor attack occurred.
- 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.