Triple
T9714826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dún Laoghaire |
E235112
|
entity |
| Predicate | hasHarbourConstructionStart |
P90395
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Dún Laoghaire, hasHarbourConstructionStart, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarbourConstructionStart Context triple: [Dún Laoghaire, hasHarbourConstructionStart, early 19th century]
-
A.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
B.
hasHarborOpened
Indicates that a harbor has been officially opened and is available for use or operation.
-
C.
hasHarborCity
Indicates that one entity possesses or is associated with a city that functions as its harbor or port.
-
D.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
-
E.
hasHarborFeature
Indicates that something possesses or includes a specific harbor-related characteristic, structure, or facility.
- F. None of above. chosen
Provenance (4 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e0a1b548190b34c8571751ca1d3 |
completed | April 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:20 p.m.