Triple
T5114816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APOE ε4 allele |
E115305
|
entity |
| Predicate | hasHigherFrequencyIn |
P13790
|
FINISHED |
| Object | people of Northern European ancestry |
—
|
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: people of Northern European ancestry | Statement: [APOE ε4 allele, hasHigherFrequencyIn, people of Northern European ancestry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHigherFrequencyIn Context triple: [APOE ε4 allele, hasHigherFrequencyIn, people of Northern European ancestry]
-
A.
hasFrequencyCategory
Indicates that something is associated with a particular classification of how often it occurs or is used.
-
B.
isHigherThan
chosen
Indicates that one entity has a greater value, level, or position than another entity.
-
C.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
D.
hasHigherClass
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
E.
hasHigherNorm
Indicates that one entity’s norm (such as magnitude, length, or size under a given norm) is greater than that of another entity.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ce6044819094166aebf0688665 |
completed | March 20, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.