Triple
T25929625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopkinsville Goblins incident of 1955 |
E653400
|
entity |
| Predicate | primaryWitnessFamily |
P58579
|
FINISHED |
| Object | Sutton family |
—
|
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: Sutton family | Statement: [Hopkinsville Goblins incident of 1955, primaryWitnessFamily, Sutton family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWitnessFamily Context triple: [Hopkinsville Goblins incident of 1955, primaryWitnessFamily, Sutton family]
-
A.
primaryFamily
Indicates that one entity is the main or principal family unit to which another entity is most closely or formally associated.
-
B.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
identifiedAsFamilyIn
chosen
Indicates that one entity is recognized or designated as a family member within the context of a specified group, record, or setting.
-
D.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
E.
mainPartyFamily
Indicates that one entity is a primary party in a relationship or event and the other entity is a family member associated with that main party.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 22, 2026, 8:36 a.m.