Triple
T14694659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lili Elbe |
E345121
|
entity |
| Predicate | legalGenderRecognition |
P115384
|
FINISHED |
| Object | 1930 |
—
|
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: 1930 | Statement: [Lili Elbe, legalGenderRecognition, 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalGenderRecognition Context triple: [Lili Elbe, legalGenderRecognition, 1930]
-
A.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
B.
genderCategories
Indicates the classification of an entity into one or more gender-related categories or identities.
-
C.
genderDivision
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
-
D.
governsGender
Indicates that one entity determines or constrains the gender classification or gender-related properties of another entity.
-
E.
genderRule
Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb586e7108190be644db9cf9a4d99 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.