Triple
T16718996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin Idumaeus |
E406295
|
entity |
| Predicate | genderForms |
P17779
|
FINISHED |
| Object | masculine: Idumaeus |
—
|
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: Idumaeus | Statement: [Latin Idumaeus, genderForms, masculine: Idumaeus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderForms Context triple: [Latin Idumaeus, genderForms, masculine: Idumaeus]
-
A.
genderedPluralForm
Indicates that the plural form of a term is specifically marked or inflected to reflect a particular gender.
-
B.
genderNeutralForm
Indicates that one entity is a gender-neutral linguistic form or expression corresponding to another, more gendered form.
-
C.
genderedFormOf
chosen
Indicates that one term is a gender-specific variant or inflected form corresponding to another, more neutral or differently gendered term.
-
D.
genderSignificance
Indicates the relevance or impact that an entity’s gender has within a particular context, relationship, or interpretation.
-
E.
genderSpecificity
Indicates whether the relationship or action applies specifically to a particular gender or is gender-neutral.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3865855108190bf8767b7b6c5fa10 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.