Triple
T24463861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cenél nÓengusa |
E616909
|
entity |
| Predicate | associatedSeaArea |
P2975
|
FINISHED |
| Object | North Channel |
E42893
|
NE 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: North Channel | Statement: [Cenél nÓengusa, associatedSeaArea, North Channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSeaArea Context triple: [Cenél nÓengusa, associatedSeaArea, North Channel]
-
A.
hasSeaAreaName
Indicates that a sea area is associated with and identified by a specific name.
-
B.
marineAreaShare
Indicates the proportion of a larger marine area that is occupied, controlled, or otherwise attributed to a specific entity.
-
C.
seaAreaA1Definition
Indicates the defined spatial extent or boundary description of a specific sea area labeled A1.
-
D.
appliesToSeaArea
Indicates that something (such as a rule, restriction, or designation) is relevant or valid within a specified sea area.
-
E.
marineArea
chosen
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
- F. None of above.
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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298cc60448190a5383d452f563834 |
completed | April 29, 2026, 11:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fe38e7d9881909468f8346c8e6a0c |
completed | May 22, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.