Triple
T28211683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brent Maverick |
E711184
|
entity |
| Predicate | primaryConflictStyle |
P5022
|
FINISHED |
| Object | verbal manipulation |
—
|
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: verbal manipulation | Statement: [Brent Maverick, primaryConflictStyle, verbal manipulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryConflictStyle Context triple: [Brent Maverick, primaryConflictStyle, verbal manipulation]
-
A.
secondaryConflict
Indicates a secondary or subordinate conflict that arises in addition to a primary or main conflict between entities.
-
B.
typicalConflict
Indicates that there is a commonly occurring or characteristic conflict or opposition between the related entities.
-
C.
centralConflictIn
Indicates that one situation, issue, or opposition serves as the primary source of tension or struggle within another context, such as a story, event, or scenario.
-
D.
mainConflict
chosen
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
E.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a000efe971081909de03f875a7ad6cc |
completed | May 10, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a000c4ffe788190a5757af60aadd9f3 |
completed | May 10, 2026, 4:40 a.m. |
Created at: April 27, 2026, 10:39 p.m.