Triple
T36172154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles Adler-Hart |
E1046172
|
entity |
| Predicate | revealsTheme |
P91427
|
FINISHED |
| Object | family relationships |
—
|
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: family relationships | Statement: [Miles Adler-Hart, revealsTheme, family relationships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealsTheme Context triple: [Miles Adler-Hart, revealsTheme, family relationships]
-
A.
themeExplores
Indicates that a work, action, or discourse centrally examines, investigates, or delves into a particular theme or subject.
-
B.
featuresThemeBy
Indicates that something (such as a work, event, or product) prominently includes or centers around a particular theme created or defined by a specified source or entity.
-
C.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
D.
reflectsOnTheme
Indicates that one entity critically considers, analyzes, or comments on the theme expressed or embodied by another entity.
-
E.
tacklesTheme
chosen
Indicates that one entity addresses, explores, or deals with a particular theme as a central subject.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:08 p.m.