Triple
T3941956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lange |
E92052
|
entity |
| Predicate | hasFeminineFormInSomeLanguages |
P52140
|
FINISHED |
| Object | Lange (unchanged) |
—
|
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: Lange (unchanged) | Statement: [Lange, hasFeminineFormInSomeLanguages, Lange (unchanged)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeminineFormInSomeLanguages Context triple: [Lange, hasFeminineFormInSomeLanguages, Lange (unchanged)]
-
A.
hasFeminineFormInCzechAndSlovak
Indicates that an entity has a specifically feminine grammatical or lexical form in the Czech and Slovak languages.
-
B.
hasMasculineForm
Indicates that an entity has a corresponding masculine grammatical or lexical form.
-
C.
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).
-
D.
hasCaseForms
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
-
E.
hasNoGrammaticalGender
Indicates that the referenced entity or term is not associated with any grammatical gender category in the relevant language system.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:24 p.m.