Triple
T26570283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ylva |
E666803
|
entity |
| Predicate | hasNameElementGender |
P104114
|
FINISHED |
| Object | feminine form of wolf |
—
|
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: feminine form of wolf | Statement: [Ylva, hasNameElementGender, feminine form of wolf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameElementGender Context triple: [Ylva, hasNameElementGender, feminine form of wolf]
-
A.
hasGenderOfPerson
Indicates that a person is associated with a specific gender classification.
-
B.
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.
-
C.
genderOfName
chosen
Indicates the gender typically associated with a given name.
-
D.
hasGenderInPortuguese
Indicates that a term or entity is associated with a specific grammatical gender in the Portuguese language.
-
E.
hasGenderFormat
Indicates that something is associated with or expressed in a particular gender-related format or representation.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 1:57 a.m.