Triple
T32609841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Venezuelans |
E833624
|
entity |
| Predicate | typicalSurnames |
P29278
|
FINISHED |
| Object | Italian surnames |
—
|
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: Italian surnames | Statement: [Italian Venezuelans, typicalSurnames, Italian surnames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSurnames Context triple: [Italian Venezuelans, typicalSurnames, Italian surnames]
-
A.
isAmongMostCommonSurnamesIn
chosen
Indicates that a surname ranks within the group of most frequently occurring surnames in a specified region or population.
-
B.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
-
C.
surnamePortmanteauOf
Indicates that one surname is formed as a portmanteau by blending parts of two or more other surnames.
-
D.
typicalFunctionInSurname
Indicates that a surname is typically associated with a particular function, role, or occupation.
-
E.
hasSurnameRank
Indicates that an entity’s surname holds a particular position or rank within an ordered set, such as a list or hierarchy of surnames.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:06 a.m.