Triple
T29600514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egerland |
E754427
|
entity |
| Predicate | relatedEthnographicGroup |
P1969
|
FINISHED |
| Object | Egerländer |
—
|
NE NERFINISHED |
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: Egerländer | Statement: [Egerland, relatedEthnographicGroup, Egerländer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEthnographicGroup Context triple: [Egerland, relatedEthnographicGroup, Egerländer]
-
A.
relatedEthnicGroup
chosen
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
B.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
C.
ethnicOrCulturalGroup
Indicates that one entity belongs to, is associated with, or is characterized by a particular ethnic or cultural group represented by the other entity.
-
D.
ethnicGroupBase
Indicates that one entity serves as the primary or foundational ethnic group from which another entity is derived, associated, or defined.
-
E.
ethnolinguisticGroups
Indicates a relationship where groups are categorized or associated based on shared ethnic and linguistic characteristics.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a017e7bdfe481909cb4d5bdede6035e |
completed | May 11, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_6a017defee108190bdf5f98dc415b250 |
completed | May 11, 2026, 6:57 a.m. |
Created at: April 28, 2026, 6:21 p.m.