Triple
T35327535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlioz |
E1020229
|
entity |
| Predicate | adoptiveFamilyMemberOf |
P12541
|
FINISHED |
| Object | Thomas O’Malley |
—
|
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: Thomas O’Malley | Statement: [Berlioz, adoptiveFamilyMemberOf, Thomas O’Malley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptiveFamilyMemberOf Context triple: [Berlioz, adoptiveFamilyMemberOf, Thomas O’Malley]
-
A.
adoptiveParent
Indicates that one entity is the legally recognized parent of another through adoption rather than biological descent.
-
B.
adoptiveFamily
chosen
Indicates a familial relationship formed through legal adoption rather than biological descent.
-
C.
adoptedSibling
Indicates that two individuals are siblings through adoption rather than by biological relation.
-
D.
adoptiveChild
Indicates that one entity is the child of another through legal adoption rather than biological descent.
-
E.
adoptiveRelationshipType
Indicates the specific nature of an adoptive relationship that exists between two entities (e.g., adoptive parent, adopted child).
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:03 p.m.