Triple
T37779971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picada Café |
E941799
|
entity |
| Predicate | primaryAncestryGroup |
P35417
|
FINISHED |
| Object | German Brazilians |
E57240
|
NE 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: German Brazilians | Statement: [Picada Café, primaryAncestryGroup, German Brazilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAncestryGroup Context triple: [Picada Café, primaryAncestryGroup, German Brazilians]
-
A.
ancestralGroup
chosen
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
B.
primaryGroup
Indicates that one entity serves as the main or most important group to which another entity primarily belongs or is associated.
-
C.
primaryAncestralCountry
Indicates the country that is considered the main place of origin for an individual’s or group’s ancestors.
-
D.
primaryRace
Indicates the main racial or ethnic category with which an entity is primarily identified or classified.
-
E.
primaryNationality
Indicates the main national affiliation or citizenship that most strongly characterizes an entity among possibly multiple nationalities.
- F. None of above.
Provenance (4 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410cafec0c819082c03086e2371907 |
completed | June 28, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.