Triple
T23128745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macassar Road |
E577107
|
entity |
| Predicate | nauticalContext |
P139259
|
FINISHED |
| Object | anchorage and nearby waters |
—
|
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: anchorage and nearby waters | Statement: [Macassar Road, nauticalContext, anchorage and nearby waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nauticalContext Context triple: [Macassar Road, nauticalContext, anchorage and nearby waters]
-
A.
maritimeUsage
Indicates the extent to which something is used for or involved in maritime activities, such as sea transport, navigation, or ocean-related operations.
-
B.
seaNavigationTradition
Indicates a tradition, practice, or custom related to navigating or traveling by sea.
-
C.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
D.
maritimeActivity
Indicates activities, operations, or behaviors that take place at sea or are directly related to maritime environments and navigation.
-
E.
nauticalRegion
chosen
Indicates that one entity is a maritime or nautical area within which the other entity is located, operates, or is relevant.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e857b40819081f9df03fff64d48 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.