Triple
T33563067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ros an Mhíl |
E859678
|
entity |
| Predicate | harbourManagedBy |
P40329
|
FINISHED |
| Object | Irish authorities |
—
|
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: Irish authorities | Statement: [Ros an Mhíl, harbourManagedBy, Irish authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harbourManagedBy Context triple: [Ros an Mhíl, harbourManagedBy, Irish authorities]
-
A.
harborManagedBy
chosen
Indicates that the operation, administration, or oversight of a harbor is carried out by a specified managing entity.
-
B.
harbourSystem
Indicates a relationship where one entity serves as a harbor or port system that accommodates, services, or supports another entity (such as ships, goods, or maritime operations).
-
C.
harbor
Indicates providing shelter, protection, or refuge for someone or something, often by keeping them in a safe or hidden place.
-
D.
harborDescription
Indicates that one entity serves as a harbor or safe anchorage location for another entity, typically providing shelter, docking, or protection.
-
E.
harbourUse
Indicates how a harbour is used or purposed, such as for specific activities, functions, or types of maritime operations.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f714fe7c819095c70dcf4164ed24 |
completed | May 3, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.