Triple
T17031253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Jones |
E413199
|
entity |
| Predicate | hasFamilyContext |
P86123
|
FINISHED |
| Object | central family in Mayberry R.F.D. |
—
|
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: central family in Mayberry R.F.D. | Statement: [Mike Jones, hasFamilyContext, central family in Mayberry R.F.D.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyContext Context triple: [Mike Jones, hasFamilyContext, central family in Mayberry R.F.D.]
-
A.
hasFamilyRelationContext
chosen
Indicates that there exists a family-based relationship or kinship context connecting the referenced entities.
-
B.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
C.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
D.
hasFamilySituation
Indicates the familial status or circumstances that apply to an entity, such as their family composition, responsibilities, or living situation.
-
E.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d9e7d481909d3d5bd241bd68f1 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.