Triple
T3862173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LFMN |
E90162
|
entity |
| Predicate | hasSeaApproach |
P12922
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LFMN, hasSeaApproach, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaApproach Context triple: [LFMN, hasSeaApproach, true]
-
A.
hasSeaAccess
chosen
Indicates that an entity has direct access to the sea, typically via a coastline, port, or navigable waterway connected to the sea.
-
B.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
C.
usesAtSea
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
-
D.
hasNotableSea
Indicates that an entity is associated with or contains a sea that is considered notable or significant.
-
E.
hasSeaCondition
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec22a5dc8190be8298d1ce8ca449 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.