Triple
T33160524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maureen O'Malley |
E848716
|
entity |
| Predicate | hasSurnameOriginCountry |
P15990
|
FINISHED |
| Object | Ireland |
—
|
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: Ireland | Statement: [Maureen O'Malley, hasSurnameOriginCountry, Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameOriginCountry Context triple: [Maureen O'Malley, hasSurnameOriginCountry, Ireland]
-
A.
hasPossibleEthnicOriginOfSurname
Indicates that a surname is associated with, or can plausibly originate from, a particular ethnic group or ethnicity.
-
B.
hasSurnameEthymology
Indicates that an entity’s surname originates from, or is derived based on, a specified source, language, or etymological root.
-
C.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
D.
usedAsSurnameInCountry
chosen
Indicates that a particular name functions as a family surname within the specified country.
-
E.
familyNameOriginType
Indicates the type or source of origin associated with a person's family name.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: May 1, 2026, 1:28 a.m.