Triple
T29756699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Loudermilk |
E753047
|
entity |
| Predicate | usesCommunicationStyle |
P83331
|
FINISHED |
| Object | brutal honesty |
—
|
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: brutal honesty | Statement: [Sam Loudermilk, usesCommunicationStyle, brutal honesty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommunicationStyle Context triple: [Sam Loudermilk, usesCommunicationStyle, brutal honesty]
-
A.
communicationTrait
chosen
Indicates a characteristic or quality related to how an entity communicates or engages in communication.
-
B.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
C.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
D.
communicationEffect
Indicates that one entity’s act of communication causes a change or effect in another entity’s state, behavior, or information.
-
E.
communicationUnderstoodBy
Indicates that a communicated message or information is successfully comprehended by the receiving entity.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 28, 2026, 7:57 p.m.