Triple
T37241617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aka people |
E923725
|
entity |
| Predicate | genderRelations |
P60410
|
FINISHED |
| Object | relatively egalitarian |
—
|
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: relatively egalitarian | Statement: [Aka people, genderRelations, relatively egalitarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderRelations Context triple: [Aka people, genderRelations, relatively egalitarian]
-
A.
relationshipWithMen
Indicates a relationship or interaction that specifically involves men as one of the parties.
-
B.
genderNorms
chosen
Indicates socially constructed expectations or rules about how individuals should behave, appear, or identify based on their perceived gender.
-
C.
featuresSameSexRelationship
Indicates that the subject includes or portrays a romantic or sexual relationship between individuals of the same sex.
-
D.
interFamilyRelations
Indicates relationships or interactions that occur between different families or family units.
-
E.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.