Triple
T32295987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Bohm |
E825098
|
entity |
| Predicate | hasSonWithSpecialAbilities |
P141946
|
FINISHED |
| Object | Jake Bohm |
—
|
NE NERFINISHED |
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: Jake Bohm | Statement: [Martin Bohm, hasSonWithSpecialAbilities, Jake Bohm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSonWithSpecialAbilities Context triple: [Martin Bohm, hasSonWithSpecialAbilities, Jake Bohm]
-
A.
hasSuperpower
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
B.
hasChildWithPsychicAbility
chosen
Indicates that an entity has at least one child who possesses a psychic or supernatural mental ability.
-
C.
believedToHaveAbility
Indicates that one entity is thought or assumed to possess a particular capability or power, without asserting that the ability is actually verified.
-
D.
sonAbility
Indicates that a son possesses or demonstrates a particular ability or capability in relation to another entity.
-
E.
hasNoSuperhumanPowers
Indicates that the subject lacks any abilities or powers beyond those of a normal human.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 12:44 a.m.