Triple
T34464771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Meath |
E884738
|
entity |
| Predicate | traditionalOverkingdomOf |
P178975
|
FINISHED |
| Object | Mide |
—
|
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: Mide | Statement: [Kingdom of Meath, traditionalOverkingdomOf, Mide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalOverkingdomOf Context triple: [Kingdom of Meath, traditionalOverkingdomOf, Mide]
-
A.
overkingdomOf
chosen
Indicates that one kingdom holds overarching authority or sovereignty over another kingdom.
-
B.
traditionalDuchy
Indicates that an entity is recognized as a duchy according to traditional or historical territorial divisions, rather than modern administrative boundaries.
-
C.
clientKingdomOf
Indicates a relationship where one kingdom is politically subordinate or tributary to another, more powerful kingdom while retaining limited internal autonomy.
-
D.
kingdom
Indicates that an entity is classified within a particular biological kingdom in a taxonomic hierarchy.
-
E.
kingdomDomain
Indicates that a kingdom is part of, or belongs within, a particular higher-level domain.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 1, 2026, 2 a.m.