Triple
T9189011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagley-class destroyer |
E220532
|
entity |
| Predicate | sawServiceDuring |
P86721
|
FINISHED |
| Object | 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: attack on Pearl Harbor | Statement: [Bagley-class destroyer, sawServiceDuring, attack on Pearl Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawServiceDuring Context triple: [Bagley-class destroyer, sawServiceDuring, attack on Pearl Harbor]
-
A.
sawServiceIn
Indicates that an entity observed or experienced a particular service within a specified context, location, or timeframe.
-
B.
sawServicePeriod
Indicates that one entity observed or was aware of the duration or specific period during which a service was provided or active.
-
C.
sawActionDuring
Indicates that one entity observed an action or event occurring within a specific time period or during another event.
-
D.
sawActionOn
Indicates that one entity visually perceived another entity performing an action.
-
E.
serviceDuring
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31d91d48190b8b8874e09c84404 |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:24 p.m.