Triple
T2964205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devonport |
E80121
|
entity |
| Predicate | isKeyRegionalPort |
P17488
|
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: [Devonport, isKeyRegionalPort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyRegionalPort Context triple: [Devonport, isKeyRegionalPort, true]
-
A.
isRegionalPort
chosen
Indicates that a port serves primarily a specific region or local area rather than functioning as a major national or international hub.
-
B.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
C.
hasRegionalIdentity
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
D.
isFromRegion
Indicates that one entity originates from, is associated with, or belongs to a specified geographic region.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9958b1e48190a77f37bf63333c5b |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.