Triple
T34872644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heʻeia Kea Pier |
E1005792
|
entity |
| Predicate | hasManagingDivision |
P68030
|
FINISHED |
| Object | Division of Boating and Ocean Recreation |
E1551970
|
NE 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: Division of Boating and Ocean Recreation | Statement: [Heʻeia Kea Pier, hasManagingDivision, Division of Boating and Ocean Recreation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManagingDivision Context triple: [Heʻeia Kea Pier, hasManagingDivision, Division of Boating and Ocean Recreation]
-
A.
hasDivisionRole
Indicates that an entity holds a specific role or position within a particular division of an organization.
-
B.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
C.
hasServiceDivision
Indicates that an entity includes or is organized into a specific service-oriented division or department.
-
D.
divisionManaged
Indicates that one entity has managerial authority or oversight responsibility over a specific division of another entity or organization.
-
E.
overseesDivision
chosen
Indicates that one entity has managerial or supervisory responsibility over a specific division of an organization.
- F. None of above.
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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01cb89ff448190b60ee3d148ce76fc |
completed | May 11, 2026, 12:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37796692bc8190bc424b312fd450f6 |
completed | June 21, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_6a01ca7604b48190bb8643c17c3a8c85 |
completed | May 11, 2026, 12:24 p.m. |
Created at: May 3, 2026, 4 p.m.