Triple
T48748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Arizona (BB-39) |
E957
|
entity |
| Predicate | homePort |
P3150
|
FINISHED |
| Object | Pearl Harbor, Hawaii (late 1930s–1941) |
—
|
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: Pearl Harbor, Hawaii (late 1930s–1941) | Statement: [USS Arizona (BB-39), homePort, Pearl Harbor, Hawaii (late 1930s–1941)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homePort Context triple: [USS Arizona (BB-39), homePort, Pearl Harbor, Hawaii (late 1930s–1941)]
-
A.
port
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
-
B.
isPortCityOn
Indicates that a city functions as a port located on the specified body of water.
-
C.
placeOfDeparture
Indicates the location from which an entity, such as a person or vehicle, begins its journey or movement.
-
D.
majorPortAtMouth
Indicates that a major port is located at the mouth of a river where it meets a larger body of water.
-
E.
homeState
Indicates that a person or organization has their primary residence, registration, or official base in a particular state.
- F. None of above. chosen
Provenance (4 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abfa7bc8190932c137a823efcb6 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24c198e74819088a211001d0b54d4 |
completed | Feb. 28, 2026, 1:59 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.