Triple
T36265368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lotterys Plus One |
E892205
|
entity |
| Predicate | featuresFamilyStructure |
P99671
|
FINISHED |
| Object | four-parent family |
—
|
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: four-parent family | Statement: [The Lotterys Plus One, featuresFamilyStructure, four-parent family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFamilyStructure Context triple: [The Lotterys Plus One, featuresFamilyStructure, four-parent family]
-
A.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
-
B.
featuresFamilyFrom
Indicates that something includes or presents a family originating from or associated with a specified source.
-
C.
familyIndicator
Indicates that there exists a familial relationship or family-based connection between the referenced entities.
-
D.
familyDescription
chosen
Indicates a descriptive statement that characterizes or summarizes the nature, structure, or dynamics of a family relationship.
-
E.
familyModel
Indicates a relationship where one entity serves as or belongs to a family-related structure, configuration, or template associated with another entity.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.