Triple
T35320206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Munster |
E1020018
|
entity |
| Predicate | overlapsModernArea |
P38212
|
FINISHED |
| Object | 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: County Cork | Statement: [South Munster, overlapsModernArea, County Cork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overlapsModernArea Context triple: [South Munster, overlapsModernArea, County Cork]
-
A.
presentDayAdministrativeAreaOverlap
chosen
Indicates that two entities share a common geographic area within their current official administrative boundaries.
-
B.
hasHistoricalRegionOverlap
Indicates that two historical regions share a common geographic area or have partially overlapping territorial extents during a given time period.
-
C.
overlapsWith
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
D.
modernAreaCorrespondsTo
Indicates that a historical or former area is associated with, or has its equivalent in, a specified modern geographic or administrative area.
-
E.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.