Triple
T35420645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Harbour |
E1023778
|
entity |
| Predicate | hasNearbyMainlandPort |
P24348
|
FINISHED |
| Object | Baltimore, County Cork |
—
|
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: Baltimore, County Cork | Statement: [South Harbour, hasNearbyMainlandPort, Baltimore, County Cork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMainlandPort Context triple: [South Harbour, hasNearbyMainlandPort, Baltimore, County Cork]
-
A.
hasNearbyFerryPort
chosen
Indicates that one location is situated close enough to another location that serves as a ferry port to be considered nearby.
-
B.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
-
C.
isPortOfCallFor
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
-
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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: May 3, 2026, 4:03 p.m.