Triple
T32935221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culmerland |
E842507
|
entity |
| Predicate | ethnicallyHistoricallyInhabitedBy |
P3032
|
FINISHED |
| Object | Poles |
—
|
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: Poles | Statement: [Culmerland, ethnicallyHistoricallyInhabitedBy, Poles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicallyHistoricallyInhabitedBy Context triple: [Culmerland, ethnicallyHistoricallyInhabitedBy, Poles]
-
A.
historicallyInhabitedBy
chosen
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
B.
historicalEthnicGroups
Indicates that there is a historically attested ethnic group or groups associated with the subject entity.
-
C.
regionHistoricalEthnonym
Indicates that a region is historically known or referred to by a particular ethnonym associated with a people or ethnic group.
-
D.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
E.
historicallyNativeTo
Indicates that an entity has been originally or traditionally present in, or originating from, a particular place or region over a significant period in history.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:20 a.m.