Triple
T13023413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Mitchell |
E326234
|
entity |
| Predicate | relationshipWithMoesha Mitchell |
P107512
|
FINISHED |
| Object | father–daughter conflict |
—
|
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: father–daughter conflict | Statement: [Frank Mitchell, relationshipWithMoesha Mitchell, father–daughter conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithMoesha Mitchell Context triple: [Frank Mitchell, relationshipWithMoesha Mitchell, father–daughter conflict]
-
A.
relationshipStatusWithMichael
Indicates the type or state of the relationship that an entity currently has with Michael.
-
B.
relationshipToMaisie
Indicates the specific type of personal or social relationship that an entity has with Maisie.
-
C.
roleOfMitchMitchell
Indicates that the specified role or function is held or performed by Mitch Mitchell.
-
D.
relationshipToEveHarrington
Indicates the nature or role of one entity’s connection or association to Eve Harrington.
-
E.
relationshipToMargoChanning
Indicates the nature or type of relationship an entity has with Margo Channing.
- F. None of above. chosen
Provenance (4 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ed05e9c8190a4f208662bca0602 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:52 p.m.