Triple
T35957755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prehistoric Estonia |
E1039914
|
entity |
| Predicate | hasPopulationOrigin |
P90644
|
FINISHED |
| Object | post-glacial hunter-gatherer groups |
—
|
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: post-glacial hunter-gatherer groups | Statement: [Prehistoric Estonia, hasPopulationOrigin, post-glacial hunter-gatherer groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopulationOrigin Context triple: [Prehistoric Estonia, hasPopulationOrigin, post-glacial hunter-gatherer groups]
-
A.
originatingPopulation
chosen
Indicates the population or group from which something (such as a sample, event, or entity) originally arises or is derived.
-
B.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
C.
raceOfOrigin
Indicates the racial or ethnic group from which an entity originally comes or is derived.
-
D.
hasEthnicOrRegionalOrigin
Indicates that an entity originates from, or is associated with, a particular ethnic group or geographic region.
-
E.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:07 p.m.