Triple
T37421554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larsen (son of Lars) |
E929867
|
entity |
| Predicate | hasGenderAssociationOfOriginalGivenName |
P34349
|
FINISHED |
| Object | masculine |
—
|
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: masculine | Statement: [Larsen (son of Lars), hasGenderAssociationOfOriginalGivenName, masculine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenderAssociationOfOriginalGivenName Context triple: [Larsen (son of Lars), hasGenderAssociationOfOriginalGivenName, masculine]
-
A.
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.
-
B.
hasGenderedFormOrigin
Indicates that one form of an entity originates from or is derived based on a specific grammatical or social gender.
-
C.
hasTypicalGenderAssociation
chosen
Indicates that one entity is commonly or culturally associated with a particular gender more than with other genders.
-
D.
hasGenderOfPerson
Indicates that a person is associated with a specific gender classification.
-
E.
hasGenderVariant
Indicates that one entity is a gender-specific form or variant of another 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 3, 2026, 4:16 p.m.