Triple
T25050070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Lookout |
E627353
|
entity |
| Predicate | hasNearbyInlet |
P23365
|
FINISHED |
| Object | Jones Inlet |
E547679
|
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: Jones Inlet | Statement: [Point Lookout, hasNearbyInlet, Jones Inlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyInlet Context triple: [Point Lookout, hasNearbyInlet, Jones Inlet]
-
A.
hasInlet
chosen
Indicates that one entity serves as an inlet or entry point through which another entity receives a flow of material, energy, or fluid.
-
B.
hasNearbySourceOf
Indicates that one entity is located close enough to another entity to serve as a relevant or accessible source of it.
-
C.
hasNearbyPortAccess
Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
-
D.
hasAdjacentCanal
Indicates that one entity is directly next to or alongside a canal.
-
E.
hasNearbyExit
Indicates that one entity has an exit located close to it in space or distance.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1075b941b88190b71b52282435fca2 |
completed | May 22, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 18, 2026, 6:09 a.m.