Triple
T21834009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michalina |
E539071
|
entity |
| Predicate | grammaticalGenderInPolish |
P122980
|
FINISHED |
| Object | feminine |
—
|
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 | Statement: [Michalina, grammaticalGenderInPolish, feminine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grammaticalGenderInPolish Context triple: [Michalina, grammaticalGenderInPolish, feminine]
-
A.
hasGenderInPolish
chosen
Indicates that an entity has a specific grammatical gender when expressed in the Polish language.
-
B.
hasGrammaticalGender
Indicates that one entity assigns or possesses a specific grammatical gender in relation to another entity (such as a word, phrase, or linguistic unit).
-
C.
grammaticalGenderInSpanish
Indicates that the entity has the specified grammatical gender (masculine, feminine, or neuter) in the Spanish language.
-
D.
hasNoGrammaticalGender
Indicates that the referenced entity or term is not associated with any grammatical gender category in the relevant language system.
-
E.
genderSignificance
Indicates the relevance or impact that an entity’s gender has within a particular context, relationship, or interpretation.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a5eeb88190b58b5b6d363cd6e3 |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.