Triple
T31541543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rí Osraige |
E804759
|
entity |
| Predicate | territorialQualifier |
P14731
|
FINISHED |
| Object | Osraige |
—
|
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: Osraige | Statement: [rí Osraige, territorialQualifier, Osraige]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territorialQualifier Context triple: [rí Osraige, territorialQualifier, Osraige]
-
A.
territorialDesignation
chosen
Indicates that an entity is assigned, defined, or recognized in terms of a specific geographic or territorial area.
-
B.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
C.
territorialStatus
Indicates the legal or political condition of control, sovereignty, or jurisdiction that applies to a specific territory.
-
D.
territorialLevel
Indicates the administrative or geographic tier at which something is defined, applied, or governed within a territorial hierarchy.
-
E.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 30, 2026, 10:06 p.m.