Triple
T14829122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ennore Port |
E348650
|
entity |
| Predicate | isAllWeatherPort |
P100449
|
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: [Ennore Port, isAllWeatherPort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAllWeatherPort Context triple: [Ennore Port, isAllWeatherPort, true]
-
A.
isDeepWaterPort
Indicates that a port has sufficiently deep water to accommodate large, heavily loaded vessels without grounding.
-
B.
isWeatherProtected
chosen
Indicates that an entity is shielded from or resistant to adverse weather conditions.
-
C.
isCommercialPort
Indicates that a location functions as a port used for commercial or trade-related maritime activities.
-
D.
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.
-
E.
isMainDeepWaterPortFor
Indicates that one location serves as the primary deep-water port facility for another entity, such as a region, city, or country.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0737d4c8190a49bf6b013da208c |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:51 a.m.