Triple
T32834474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Home at the End of the World |
E839786
|
entity |
| Predicate | exploresNonTraditionalFamily |
P176074
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [A Home at the End of the World, exploresNonTraditionalFamily, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresNonTraditionalFamily Context triple: [A Home at the End of the World, exploresNonTraditionalFamily, true]
-
A.
cultFamily
Indicates that one entity is a family member of another within the context of a cult or cult-like group.
-
B.
interFamilyRelations
Indicates relationships or interactions that occur between different families or family units.
-
C.
multiGenerationalFamilyFocus
Indicates a focus on relationships, dynamics, or activities that span multiple generations within the same family.
-
D.
familyDivision
Indicates a relationship where a family is split into distinct parts or groups, often due to conflict, separation, or differing affiliations.
-
E.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:16 a.m.