Triple
T1083740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 77th United States Congress |
E24004
|
entity |
| Predicate | respondedToEvent |
P17506
|
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: [77th United States Congress, respondedToEvent, attack on Pearl Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: respondedToEvent Context triple: [77th United States Congress, respondedToEvent, attack on Pearl Harbor]
-
A.
dealtWithEvent
chosen
Indicates that an entity has handled, responded to, or otherwise taken action to address a particular event.
-
B.
connectedToEvent
Indicates that an entity has a direct association or linkage with a specific event.
-
C.
respondsTo
Indicates that one entity replies or reacts to a message, action, or stimulus originating from another entity.
-
D.
hadListeningEventAt
Indicates that a listening event involving an entity occurred at a specific time or place.
-
E.
facedEvent
Indicates that an entity directly encountered, experienced, or dealt with a particular 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9608bac819085196cc0f8fbb2e7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.