Triple
T8375909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Pickle |
E197573
|
entity |
| Predicate | personalLife |
P4083
|
FINISHED |
| Object | closeted for many years |
—
|
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: closeted for many years | Statement: [Frank Pickle, personalLife, closeted for many years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalLife Context triple: [Frank Pickle, personalLife, closeted for many years]
-
A.
hasPersonalLife
Indicates that an entity has aspects, activities, or relationships belonging to its private or non-professional life.
-
B.
roleInIndividualLife
Indicates the specific function, influence, or involvement that one entity has within the personal life or experiences of another entity.
-
C.
lifeDetails
chosen
Indicates that additional information or specific aspects about an entity’s life (such as background, experiences, or personal history) are being described.
-
D.
partnerInLifeEvent
Indicates that two or more entities share a partnership or joint involvement in a specific life event or milestone.
-
E.
followsLifeOf
Indicates that one entity’s narrative, development, or progression is tracked or depicted over the course of that entity’s life.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80bf6b8081909b98762b1f900bef |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.