Triple
T13002840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belasí |
E322210
|
entity |
| Predicate | genderInSlovak |
P107779
|
FINISHED |
| Object | masculine plural adjective |
—
|
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 plural adjective | Statement: [Belasí, genderInSlovak, masculine plural adjective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderInSlovak Context triple: [Belasí, genderInSlovak, masculine plural adjective]
-
A.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
B.
hasFeminineFormInCzechAndSlovak
Indicates that an entity has a specifically feminine grammatical or lexical form in the Czech and Slovak languages.
-
C.
genderSignificance
Indicates the relevance or impact that an entity’s gender has within a particular context, relationship, or interpretation.
-
D.
genderInOldNorse
Indicates the grammatical gender that a given entity has in the Old Norse language.
-
E.
genderDivision
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
- F. None of above. chosen
Provenance (4 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9a2a448190968833354280e474 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e74283c819082e69ac3554fa7d8 |
completed | April 10, 2026, 10:49 p.m. |
Created at: April 9, 2026, 8:47 p.m.