Triple
T28684103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Pearl Harbor Board |
E726083
|
entity |
| Predicate | reportCompleted |
P135621
|
FINISHED |
| Object | 1944 |
—
|
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: 1944 | Statement: [Army Pearl Harbor Board, reportCompleted, 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportCompleted Context triple: [Army Pearl Harbor Board, reportCompleted, 1944]
-
A.
reportsOutcomeOf
Indicates that one entity communicates or provides the result, consequence, or final status of another entity’s process, event, or action.
-
B.
completionOf
chosen
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
-
C.
report
Indicates that one entity formally provides information or an account about another entity, event, or situation, typically for documentation, communication, or evaluation purposes.
-
D.
reportsFormat
Indicates that one entity reports or presents information in a particular format specified by another entity.
-
E.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 5:11 a.m.