Triple
T28815139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymond FitzGerald |
E727620
|
entity |
| Predicate | territoryAssociatedWith |
P21614
|
FINISHED |
| Object | Leinster |
—
|
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: Leinster | Statement: [Raymond FitzGerald, territoryAssociatedWith, Leinster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territoryAssociatedWith Context triple: [Raymond FitzGerald, territoryAssociatedWith, Leinster]
-
A.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
-
B.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
C.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
D.
affectsTerritoryOf
Indicates that one entity causes changes to, or has an impact on, the territorial domain or jurisdiction of another entity.
-
E.
hasTerritorialAssociation
chosen
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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:32 a.m.