Triple
T21737977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Daly |
E536575
|
entity |
| Predicate | privateBehavior |
P145172
|
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: [Robert Daly, privateBehavior, abusive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privateBehavior Context triple: [Robert Daly, privateBehavior, abusive]
-
A.
defaultBehavior
Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
-
B.
previousBehavior
Indicates that an entity’s past actions, conduct, or patterns of behavior are being referenced in relation to a current context or evaluation.
-
C.
definingBehavior
Indicates the characteristic action or pattern of actions that fundamentally determines or typifies how something functions or is understood.
-
D.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
E.
behaviorCode
Indicates the specific rule, standard, or classification code that governs or characterizes an entity’s behavior in a given context.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd0d33dc81908a4a79abc33355d1 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69f3ed4408190a4a78410bf660c44 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 6:49 p.m.