Triple
T33383105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burning Secret |
E854835
|
entity |
| Predicate | hasBaronCharacterTrait |
P192317
|
FINISHED |
| Object | manipulative |
—
|
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: manipulative | Statement: [Burning Secret, hasBaronCharacterTrait, manipulative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaronCharacterTrait Context triple: [Burning Secret, hasBaronCharacterTrait, manipulative]
-
A.
hasSupportingCharacterTrait
Indicates that a supporting character possesses a particular trait, quality, or characteristic.
-
B.
hasBaritoneRole
Indicates that an entity holds or performs a role specifically designated for the baritone voice range.
-
C.
hasCharacterAbility
Indicates that a character possesses or can perform a specific ability.
-
D.
hasPrimaryBartenderTrait
Indicates that an entity possesses the main or defining characteristic(s) associated with being a bartender.
-
E.
notableLeaderTrait
Indicates that the specified trait is a particularly prominent or defining characteristic of the leader in question.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: May 1, 2026, 1:35 a.m.