Triple
T37270614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solor Archipelago |
E924501
|
entity |
| Predicate | hasPortTowns |
P2745
|
FINISHED |
| Object | Larantuka (nearby gateway on Flores) |
—
|
NE NERFINISHED |
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: Larantuka (nearby gateway on Flores) | Statement: [Solor Archipelago, hasPortTowns, Larantuka (nearby gateway on Flores)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortTowns Context triple: [Solor Archipelago, hasPortTowns, Larantuka (nearby gateway on Flores)]
-
A.
isPortTown
Indicates that a town is located on or near a navigable body of water and functions as a port for maritime or river transport and trade.
-
B.
hasPortCity
chosen
Indicates that a place or region possesses or is associated with a city that functions as its port.
-
C.
hasPortTownService
Indicates that a service or connection is available between a port and a town.
-
D.
isPortCityOn
Indicates that a city functions as a port located on the specified body of water.
-
E.
isHomePortOf
Indicates that a particular location serves as the primary base or port where a vessel or fleet is officially registered, stationed, or regularly returns.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: May 3, 2026, 4:15 p.m.