Triple
T36241325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mokil Atoll |
E891524
|
entity |
| Predicate | transportBySeaTo |
P14751
|
FINISHED |
| Object | Pohnpei |
—
|
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: Pohnpei | Statement: [Mokil Atoll, transportBySeaTo, Pohnpei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportBySeaTo Context triple: [Mokil Atoll, transportBySeaTo, Pohnpei]
-
A.
shipsTo
Indicates that one entity sends or delivers goods, products, or items to another entity or location.
-
B.
controlledSeaRoute
Indicates that one entity has authority over, or the ability to regulate and manage access through, a particular maritime route used for navigation or transport.
-
C.
shipCompanion
Indicates that one entity serves as a companion or partner accompanying another entity on a ship or sea voyage.
-
D.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
E.
waterTransport
chosen
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
- 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 3, 2026, 4:09 p.m.