Triple
T2134569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giacomo |
E46619
|
entity |
| Predicate | typicalBearersGender |
P34342
|
FINISHED |
| Object | male |
—
|
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: male | Statement: [Giacomo, typicalBearersGender, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBearersGender Context triple: [Giacomo, typicalBearersGender, male]
-
A.
genderOfTypicalHolder
chosen
Indicates the gender that is most commonly associated with or typical of the usual holder of something.
-
B.
hasTypicalGenderAssociation
Indicates that one entity is commonly or culturally associated with a particular gender more than with other genders.
-
C.
namedForGender
Indicates that one entity is named in a way that reflects or is derived from a particular gender or gender-related characteristic of another entity.
-
D.
genderRule
Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
-
E.
hasNumberOfGenders
Indicates the relationship that specifies how many distinct genders are associated with or recognized for a given entity.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbba24004819091ffb9440e8615fa |
completed | March 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.