Triple
T15712283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honoapiʻilani Highway |
E380867
|
entity |
| Predicate | isPrimaryAccessRouteTo |
P55123
|
FINISHED |
| Object | Lahaina area |
—
|
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: Lahaina area | Statement: [Honoapiʻilani Highway, isPrimaryAccessRouteTo, Lahaina area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryAccessRouteTo Context triple: [Honoapiʻilani Highway, isPrimaryAccessRouteTo, Lahaina area]
-
A.
hasPrimaryAccessFrom
Indicates that one entity serves as the main or preferred point of access or entry to another entity.
-
B.
isAccessRouteAround
Indicates that one entity serves as an access route that goes around or circumvents another entity.
-
C.
hasAccessRouteTo
Indicates that one entity possesses a path, connection, or means of reaching or interacting with another entity.
-
D.
hasPrimaryAccessType
Indicates that an entity is associated with its main or default mode or category of access.
-
E.
hasPrimaryRoute
chosen
Indicates that one entity is designated as the main or principal route associated with another entity.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f8f5d6081908243fa59b46b7c76 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.