Triple
T28684074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Pearl Harbor Board |
E726083
|
entity |
| Predicate | locationOfEventsInvestigated |
P58123
|
FINISHED |
| Object | Pearl Harbor |
—
|
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: Pearl Harbor | Statement: [Army Pearl Harbor Board, locationOfEventsInvestigated, Pearl Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfEventsInvestigated Context triple: [Army Pearl Harbor Board, locationOfEventsInvestigated, Pearl Harbor]
-
A.
investigatedEvent
Indicates that an event was the subject of an investigation or inquiry carried out by some agent.
-
B.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
C.
tookPlaceAtLocation
Indicates that an event or action occurred at a specific location.
-
D.
investigatesAt
Indicates that an entity conducts an investigation or research activity at a specific location or institution.
-
E.
investigatedPlace
chosen
Indicates that an agent carried out an investigation or inquiry at a particular place or location.
- 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_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: April 28, 2026, 5:11 a.m.