Triple
T25487083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skinner family (speculative) |
E638739
|
entity |
| Predicate | hasDocumentedMembers |
P7638
|
FINISHED |
| Object | unknown |
—
|
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: unknown | Statement: [Skinner family (speculative), hasDocumentedMembers, unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDocumentedMembers Context triple: [Skinner family (speculative), hasDocumentedMembers, unknown]
-
A.
isBetterDocumentedMemberOf
Indicates that one entity is a member of a group or set whose documentation quality is higher or more complete than that of comparable members.
-
B.
hasMembersWith
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
-
C.
hasMembers
chosen
Indicates that a group, organization, or collection includes certain entities as its members.
-
D.
isWidelyDocumented
Indicates that extensive and accessible documentation or records exist about the subject across multiple reputable sources.
-
E.
hasLimitedDocumentation
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f77d26488190898b7befa111282b |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:32 p.m.