Triple
T6346689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County Leitrim |
E142761
|
entity |
| Predicate | hasAtlanticCoastlineLength |
P1896
|
FINISHED |
| Object | short stretch |
—
|
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: short stretch | Statement: [County Leitrim, hasAtlanticCoastlineLength, short stretch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAtlanticCoastlineLength Context triple: [County Leitrim, hasAtlanticCoastlineLength, short stretch]
-
A.
shorelineLength
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
-
B.
hasCoastline
chosen
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
C.
influencedCoastlineOf
Indicates that one entity has affected, shaped, or altered the characteristics, form, or condition of another entity’s coastline.
-
D.
hasLongestCoastlineCountry
Indicates that the subject is the country possessing the longest total coastline length among a specified set or within a given context.
-
E.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067b907c4819085a3ea87589bc4be |
completed | March 22, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.