Triple
T6746775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samaritans |
E154236
|
entity |
| Predicate | genePool |
P31423
|
FINISHED |
| Object | shows continuity with ancient Levantine populations |
—
|
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: shows continuity with ancient Levantine populations | Statement: [Samaritans, genePool, shows continuity with ancient Levantine populations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genePool Context triple: [Samaritans, genePool, shows continuity with ancient Levantine populations]
-
A.
gens
Indicates a relationship where one entity generates, produces, or gives rise to another entity.
-
B.
winnerGeneration
Indicates that an entity is responsible for producing, determining, or designating the winner in a given context or competition.
-
C.
geneticExchange
chosen
Indicates the transfer or sharing of genetic material between entities, resulting in altered or recombined genetic information.
-
D.
genesis
Indicates the origin, creation, or initial emergence of one entity from another or from a particular source or cause.
-
E.
generationOf
Indicates that one entity is the origin, creator, or producer 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1b8a0f0819086b802983e8ffcb6 |
completed | March 27, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:10 p.m.