Triple
T31217814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innocent |
E795919
|
entity |
| Predicate | behaviorCharacterizedBy |
P37384
|
FINISHED |
| Object | eccentric actions |
—
|
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: eccentric actions | Statement: [Innocent, behaviorCharacterizedBy, eccentric actions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorCharacterizedBy Context triple: [Innocent, behaviorCharacterizedBy, eccentric actions]
-
A.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
associatedCharacterTrait
chosen
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
C.
declineCharacterizedBy
Indicates that a decline or deterioration is defined, described, or distinguished by a particular feature, symptom, or characteristic.
-
D.
periodCharacterizedBy
Indicates that a specific time period is defined or distinguished by a particular characteristic, condition, or feature.
-
E.
relationshipCharacterizedAs
Indicates that one relationship is described, defined, or typified in terms of another specified characteristic or relational type.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:10 p.m.