Triple
T17082369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcellino |
E414504
|
entity |
| Predicate | isCommonInOnomasticsCategory |
P34347
|
FINISHED |
| Object | Italian masculine given names |
—
|
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 masculine given names | Statement: [Marcellino, isCommonInOnomasticsCategory, Italian masculine given names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonInOnomasticsCategory Context triple: [Marcellino, isCommonInOnomasticsCategory, Italian masculine given names]
-
A.
commonInOnomastics
chosen
Indicates that a name, term, or pattern frequently appears or is widely used within the study and practice of naming (onomastics).
-
B.
isCommonAsFirstName
Indicates that the referenced name is frequently used as a first (given) name within a specified population or context.
-
C.
isCommonToponym
Indicates that a place name is widely used or shared by multiple distinct locations.
-
D.
isCommonAsMiddleName
Indicates that a given name is frequently used as a middle name rather than as a first or last name.
-
E.
isAlsoCommonNounInLanguage
Indicates that an entity is also used as a common noun in a specified language.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe408d48190b4f52c2102eae7c2 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.