Triple
T27906080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascanio von Cramm |
E705782
|
entity |
| Predicate | hasFamilyReputationFor |
P150229
|
FINISHED |
| Object | historical influence |
—
|
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: historical influence | Statement: [Ascanio von Cramm, hasFamilyReputationFor, historical influence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyReputationFor Context triple: [Ascanio von Cramm, hasFamilyReputationFor, historical influence]
-
A.
hasFamilyReputation
Indicates that an entity is associated with a particular standing, status, or reputation held by their family.
-
B.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
C.
isFromFamilyKnownFor
chosen
Indicates that an entity belongs to a family that is widely recognized or notable for a particular characteristic, achievement, or reputation.
-
D.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
E.
hasQuirkyReputation
Indicates that an entity is regarded by others as having an unusual, eccentric, or unconventional character or style.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 6:45 p.m.