Triple
T534245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battleship Row, Pearl Harbor |
E12291
|
entity |
| Predicate | coordinateRoleInEvent |
P4073
|
FINISHED |
| Object | focal point of Japanese 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: focal point of Japanese attack on Pearl Harbor | Statement: [Battleship Row, Pearl Harbor, coordinateRoleInEvent, focal point of Japanese attack on Pearl Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateRoleInEvent Context triple: [Battleship Row, Pearl Harbor, coordinateRoleInEvent, focal point of Japanese attack on Pearl Harbor]
-
A.
eventRole
chosen
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
B.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
C.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
D.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
E.
unionEvent
Indicates an event in which two or more entities are joined or combined into a single unified whole.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.