Triple
T33142281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eóganacht Airthir Cliach |
E848186
|
entity |
| Predicate | hasTerritorialOrientation |
P45984
|
FINISHED |
| Object | eastern |
—
|
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: eastern | Statement: [Eóganacht Airthir Cliach, hasTerritorialOrientation, eastern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerritorialOrientation Context triple: [Eóganacht Airthir Cliach, hasTerritorialOrientation, eastern]
-
A.
hasTerritorialDimension
Indicates that something possesses or involves a spatial or territorial extent, scope, or jurisdiction.
-
B.
hasRegionalOrientation
chosen
Indicates that an entity is oriented toward, focused on, or primarily associated with a specific geographic region.
-
C.
regionalOrientation
Indicates how something is directed, aligned, or focused toward a particular geographic region or area.
-
D.
territorial
Indicates that one entity claims, defends, or is associated with control over a specific area or domain in relation to another entity.
-
E.
hasTerritorialAssociation
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 1, 2026, 1:28 a.m.