Triple
T33598781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millicent "Mil" Parker |
E860655
|
entity |
| Predicate | coreThemeAssociation |
P176949
|
FINISHED |
| Object | personal turmoil |
—
|
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: personal turmoil | Statement: [Millicent "Mil" Parker, coreThemeAssociation, personal turmoil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreThemeAssociation Context triple: [Millicent "Mil" Parker, coreThemeAssociation, personal turmoil]
-
A.
primaryThemeAssociation
Indicates that one entity is the main or central theme associated with another entity.
-
B.
majorThemeAssociation
Indicates that one entity is associated with another as a primary or central theme.
-
C.
associatedThemeElements
Indicates a relationship where certain elements are linked to, or grouped under, a particular theme as its related components.
-
D.
hasThemeRelationship
Indicates a relationship where one entity is thematically related to, or centered around, another entity as its main subject or topic.
-
E.
themeKey
Indicates that one entity serves as the primary subject, topic, or thematic focus associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:41 a.m.