Triple
T13681643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TEV |
E328016
|
entity |
| Predicate | usesGenderInclusiveLanguage |
P11531
|
FINISHED |
| Object | partially |
—
|
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: partially | Statement: [TEV, usesGenderInclusiveLanguage, partially]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGenderInclusiveLanguage Context triple: [TEV, usesGenderInclusiveLanguage, partially]
-
A.
usesGenderAccurateLanguage
Indicates that the language employed in the context correctly reflects and respects the gender identities of the entities referenced.
-
B.
usesInclusiveLanguage
chosen
Indicates that the subject communicates in a way that avoids biased, exclusionary, or discriminatory language toward any group.
-
C.
hasGenderNeutrality
Indicates that something (such as a term, form, or expression) is neutral with respect to gender and does not specify or imply any particular gender.
-
D.
genderInclusiveProgram
Indicates that a program is designed and implemented to be inclusive and respectful of all genders, avoiding bias or exclusion based on gender identity or expression.
-
E.
hasNeutralPronoun
Indicates that an entity is referred to using a gender-neutral pronoun.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.