Triple
T8974216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitzwilliam |
E214343
|
entity |
| Predicate | regionOfAssociation |
P86016
|
FINISHED |
| Object | Anglo-Irish aristocracy |
—
|
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: Anglo-Irish aristocracy | Statement: [Fitzwilliam, regionOfAssociation, Anglo-Irish aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfAssociation Context triple: [Fitzwilliam, regionOfAssociation, Anglo-Irish aristocracy]
-
A.
associatedAdministrativeRegion
Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
-
B.
hasTerritorialAssociation
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
E.
regionReference
Indicates that one entity refers to, points to, or is associated with a specific region or area defined by another entity.
- F. None of above. chosen
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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6783abe48190840e652fc2acf28f |
completed | April 1, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5fcf24348190b6b845205161c0ee |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:02 p.m.