Triple
T28684085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Pearl Harbor Board |
E726083
|
entity |
| Predicate | conductedHearingsIn |
P11604
|
FINISHED |
| Object | Hawaii |
—
|
NE NERFINISHED |
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: Hawaii | Statement: [Army Pearl Harbor Board, conductedHearingsIn, Hawaii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conductedHearingsIn Context triple: [Army Pearl Harbor Board, conductedHearingsIn, Hawaii]
-
A.
heldPublicHearings
chosen
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
B.
hearingsType
Indicates the specific category or kind of hearing associated with a given case or proceeding.
-
C.
hearsAppealsIn
Indicates that a judicial body has the authority to review and decide appeals within a specified jurisdiction or court.
-
D.
hearsProceedingsBroughtBy
Indicates that a judicial or administrative body formally considers and adjudicates legal proceedings initiated by a particular party.
-
E.
hearsAppealsBy
Indicates that one party has the authority or role to review and decide on appeals submitted by another party.
- 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_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:11 a.m.