Triple
T31142864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Upper Ossory |
E793836
|
entity |
| Predicate | associatedEthnoSocialGroup |
P194225
|
FINISHED |
| Object | Anglo-Irish |
—
|
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 | Statement: [Baron Upper Ossory, associatedEthnoSocialGroup, Anglo-Irish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedEthnoSocialGroup Context triple: [Baron Upper Ossory, associatedEthnoSocialGroup, Anglo-Irish]
-
A.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
B.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
C.
containedEthnicGroup
Indicates that one entity (typically a larger group, region, or population) includes or encompasses a particular ethnic group within it.
-
D.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
-
E.
ethnicGroupOfMembers
chosen
Indicates that a specified ethnic group is the ethnic affiliation shared by the members of a given group or organization.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:06 p.m.