Triple
T2936171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Compson III |
E79272
|
entity |
| Predicate | behaviorTowardOthers |
P12438
|
FINISHED |
| Object | abusive |
—
|
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: abusive | Statement: [Jason Compson III, behaviorTowardOthers, abusive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorTowardOthers Context triple: [Jason Compson III, behaviorTowardOthers, abusive]
-
A.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
B.
socialOrientation
chosen
Indicates the nature or direction of an entity’s social tendencies, such as how it typically relates to, interacts with, or aligns itself within social contexts or groups.
-
C.
behaviorObserved
Indicates that a particular behavior or action has been witnessed, recorded, or detected in relation to an entity or context.
-
D.
associatedCharacterTrait
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
E.
addressesBehavior
Indicates that one entity’s actions or policies are directed toward managing, influencing, or responding to the behavior of another 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983df5e08190939cd8acf8ad5b55 |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.