Triple
T37784249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O'Brien family |
E941909
|
entity |
| Predicate | traditionalSurnameForm |
P121268
|
FINISHED |
| Object | Ó Briain |
—
|
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: Ó Briain | Statement: [O'Brien family, traditionalSurnameForm, Ó Briain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalSurnameForm Context triple: [O'Brien family, traditionalSurnameForm, Ó Briain]
-
A.
usedSurnameFor
Indicates that one entity adopted or employed another entity’s surname as the name by which they were known or referred to.
-
B.
laterFamilyNameForm
chosen
Indicates that one family name is a later or subsequent form of another family name, reflecting a change or evolution over time.
-
C.
pairedTraditionalName
Indicates that two entities are associated as a traditional name pair, typically used together or in customary combination within a cultural or naming convention.
-
D.
familyNameSuffix
Indicates that one entity is the suffix portion (such as “Jr.” or “III”) of another entity’s family name.
-
E.
traditionalDescendants
Indicates that one entity is a descendant of another according to traditional or customary lineage or inheritance rules.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
Created at: May 3, 2026, 4:19 p.m.