Triple
T30574750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex Hiberniae |
E778212
|
entity |
| Predicate | caseOfHiberniae |
P169863
|
FINISHED |
| Object | genitive plural of Hibernia |
—
|
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: genitive plural of Hibernia | Statement: [Rex Hiberniae, caseOfHiberniae, genitive plural of Hibernia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseOfHiberniae Context triple: [Rex Hiberniae, caseOfHiberniae, genitive plural of Hibernia]
-
A.
GoidelicNationsInclude
Indicates that a specified set or group of nations includes those belonging to the Goidelic (Gaelic-speaking) cultural-linguistic tradition.
-
B.
caseOfScottorum
Indicates that something pertains to, is associated with, or is characteristic of the Scots or Scotland.
-
C.
JórvíkIs
Indicates that one entity is identified as or equated with Jórvík (the historical name for York), expressing that they are the same place or concept.
-
D.
الأصل التاريخي
Indicates the historical origin or source from which something or someone is derived.
-
E.
hadKingdom
Indicates that an entity possessed or ruled over a particular kingdom.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689167878819093cb4f58efd47e2e |
completed | May 2, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:22 p.m.