Triple
T2915439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deandra "Sweet Dee" Reynolds |
E78593
|
entity |
| Predicate | frequentActivity |
P1164
|
FINISHED |
| Object | scheming with the gang |
—
|
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: scheming with the gang | Statement: [Deandra "Sweet Dee" Reynolds, frequentActivity, scheming with the gang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentActivity Context triple: [Deandra "Sweet Dee" Reynolds, frequentActivity, scheming with the gang]
-
A.
typicalActivity
chosen
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
B.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
C.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
D.
coordinatesActivitiesOf
Indicates that one entity organizes, aligns, or manages the activities of another entity or group of entities so they work together effectively.
-
E.
majorActivity
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:50 p.m.