Triple
T38125584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunne |
E952057
|
entity |
| Predicate | hasPrimaryLocationHistorically |
P76442
|
FINISHED |
| Object | County Laois |
E260995
|
NE 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: County Laois | Statement: [Dunne, hasPrimaryLocationHistorically, County Laois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryLocationHistorically Context triple: [Dunne, hasPrimaryLocationHistorically, County Laois]
-
A.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
B.
historicallyLocatedOutside
Indicates that an entity was historically situated beyond the boundaries or limits of another specified place or region.
-
C.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
-
D.
hasHomeRegionHistorical
Indicates that an entity is historically associated with or originates from a particular home region.
-
E.
primaryLocationHistoric
chosen
Indicates the historically primary or most significant location associated with an entity, such as where it was originally based, founded, or chiefly active in the past.
- F. None of above.
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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4167f7e2308190b4a8622e1af03f0e |
completed | June 28, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.