Triple
T18317565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheikh |
E438786
|
entity |
| Predicate | canBeHereditary |
P103215
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sheikh, canBeHereditary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeHereditary Context triple: [Sheikh, canBeHereditary, true]
-
A.
oftenHereditary
chosen
Indicates that the relationship or property typically passes from parents to offspring through genetic inheritance.
-
B.
hereditaryInFamily
Indicates that a trait, condition, or characteristic is passed down through generations within the same family.
-
C.
hasGeneticInheritancePattern
Indicates that there is a specific mode or pattern by which genetic traits or conditions are transmitted from one generation to the next.
-
D.
hasHereditaryNumber
Indicates that an entity is associated with a specific hereditary identifier or sequence number passed down through a lineage or inheritance chain.
-
E.
nonHereditary
Indicates that a trait, condition, or status is not passed down genetically from parents to offspring.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021f5f1081909fd98c8fb786c7ff |
completed | April 19, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.