Triple
T38399309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loígis |
E900851
|
entity |
| Predicate | regionNowMostlyIn |
P8402
|
FINISHED |
| Object | County Laois |
—
|
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: County Laois | Statement: [Loígis, regionNowMostlyIn, County Laois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionNowMostlyIn Context triple: [Loígis, regionNowMostlyIn, County Laois]
-
A.
currentTerritoryMostlyIn
chosen
Indicates that the majority of the current territorial area of one entity lies within the territorial boundaries of another entity.
-
B.
regionIs
Indicates that one entity is located within, belongs to, or is associated with a specified geographic or administrative region.
-
C.
areaRuledNowIn
Indicates that a region is currently governed or controlled by a specified ruling authority or entity.
-
D.
administrativeRegionMostlyCoincidesWith
Indicates that the spatial extent of one administrative region substantially overlaps and aligns with that of another, with only minor differences in boundaries.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
Created at: May 3, 2026, 4:31 p.m.