Triple
T6329143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tutty Bomowski |
E141932
|
entity |
| Predicate | relationshipToJoeBomowski |
P66770
|
FINISHED |
| Object | mother |
—
|
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: mother | Statement: [Tutty Bomowski, relationshipToJoeBomowski, mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToJoeBomowski Context triple: [Tutty Bomowski, relationshipToJoeBomowski, mother]
-
A.
relationshipToJoeKeller
chosen
Indicates the specific familial, social, or personal connection that one entity has to Joe Keller.
-
B.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
C.
relationshipToNaomi
Indicates the specific familial, social, or interpersonal connection that an entity has with Naomi.
-
D.
relationshipToBenjy
Indicates the specific type of relationship or connection an entity has to Benjy.
-
E.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651197908190a30e504e2442d40f |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.