Triple
T30053108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2101 Records |
E763654
|
entity |
| Predicate | hasEthnicBackgroundOfFounder |
P159726
|
FINISHED |
| Object | Moroccan-Swedish |
—
|
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: Moroccan-Swedish | Statement: [2101 Records, hasEthnicBackgroundOfFounder, Moroccan-Swedish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicBackgroundOfFounder Context triple: [2101 Records, hasEthnicBackgroundOfFounder, Moroccan-Swedish]
-
A.
hasFounderEthnicity
chosen
Indicates that an entity has a founder whose ethnicity is the specified value.
-
B.
hasEthnicOrRegionalOrigin
Indicates that an entity originates from, or is associated with, a particular ethnic group or geographic region.
-
C.
hasEthnicInfluence
Indicates that one entity has a cultural, traditional, or ethnic impact on, or contributes to shaping the ethnic character of, another entity.
-
D.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
E.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 6:56 p.m.