Triple
T35655393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uí Chonchobhair |
E1030268
|
entity |
| Predicate | belongsToSurnameGroup |
P150358
|
FINISHED |
| Object | Ó Conchobhair / O'Connor surnames |
—
|
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: Ó Conchobhair / O'Connor surnames | Statement: [Uí Chonchobhair, belongsToSurnameGroup, Ó Conchobhair / O'Connor surnames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToSurnameGroup Context triple: [Uí Chonchobhair, belongsToSurnameGroup, Ó Conchobhair / O'Connor surnames]
-
A.
belongsToFamilyCommonName
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
B.
correspondsToSurname
chosen
Indicates that one entity is the surname or family name associated with, matching, or representing the other entity.
-
C.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
-
D.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
E.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:05 p.m.