Triple
T17421127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neumark region |
E423616
|
entity |
| Predicate | ethnicallyMixed |
P42257
|
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: [Neumark region, ethnicallyMixed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicallyMixed Context triple: [Neumark region, ethnicallyMixed, true]
-
A.
hasEthnicallyMixedPopulation
chosen
Indicates that a population is composed of people from multiple distinct ethnic groups rather than being ethnically homogeneous.
-
B.
includesMixedSexRace
Indicates that the group or context involves individuals of more than one sex and more than one race.
-
C.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
D.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
-
E.
involvedEthnicGroup
Indicates that a particular ethnic group participates in, is affected by, or is otherwise associated with the referenced event, situation, or 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e442372954819085f332efc7067ae9 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.