Triple
T2435774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania German |
E52955
|
entity |
| Predicate | grammaticalGenderSystem |
P11611
|
FINISHED |
| Object | three-gender system |
—
|
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: three-gender system | Statement: [Pennsylvania German, grammaticalGenderSystem, three-gender system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grammaticalGenderSystem Context triple: [Pennsylvania German, grammaticalGenderSystem, three-gender system]
-
A.
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).
-
B.
hasNoGrammaticalGender
Indicates that the referenced entity or term is not associated with any grammatical gender category in the relevant language system.
-
C.
hasGenderSystem
chosen
Indicates that an entity employs or is characterized by a particular system for categorizing gender.
-
D.
hasPronounSystem
Indicates that an entity possesses or employs a particular system or set of rules for using pronouns.
-
E.
grammaticalPerson
Indicates the grammatical role of a participant in speech (such as first, second, or third person) in relation to the speaker and listener.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.