Triple
T25006637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fat Charlie Nancy |
E625856
|
entity |
| Predicate | hasFutureFatherInLaw |
P60016
|
FINISHED |
| Object | Maurice Noah |
—
|
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: Maurice Noah | Statement: [Fat Charlie Nancy, hasFutureFatherInLaw, Maurice Noah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFutureFatherInLaw Context triple: [Fat Charlie Nancy, hasFutureFatherInLaw, Maurice Noah]
-
A.
futureFatherInLaw
chosen
Indicates that one person is the father of another person's future spouse, i.e., will become their father-in-law through an anticipated marriage.
-
B.
possibleFatherInLaw
Indicates that one person is a potential or candidate father-in-law of another, typically as the (possible) father of that person’s spouse or prospective spouse.
-
C.
fatherInLaw
Indicates a relationship where one person is the father of another person's spouse or the spouse of someone's parent.
-
D.
hasGreatNephew
Indicates that one person is the great-nephew (the grandson of a sibling) of another person.
-
E.
hasFatherFigure
Indicates that one entity serves as a paternal or father-like figure to another entity, regardless of biological relation.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b113f8c8190ae05102e9c2ae076 |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:05 a.m.