Triple
T24294891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asr |
E605929
|
entity |
| Predicate | genderRuling |
P29781
|
FINISHED |
| Object | obligatory for adult men and women |
—
|
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: obligatory for adult men and women | Statement: [Asr, genderRuling, obligatory for adult men and women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderRuling Context triple: [Asr, genderRuling, obligatory for adult men and women]
-
A.
genderRule
chosen
Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
-
B.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
C.
genderDivision
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
-
D.
genderImplication
Indicates that one entity’s gender suggests, constrains, or determines the possible or likely gender of another entity.
-
E.
genderOfName
Indicates the gender typically associated with a given name.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f291593c0881908a6827f0d8899fe6 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.