Triple
T19549958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruby |
E489170
|
entity |
| Predicate | hasSocialDivision |
P94536
|
FINISHED |
| Object | strict gender roles |
—
|
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: strict gender roles | Statement: [Ruby, hasSocialDivision, strict gender roles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialDivision Context triple: [Ruby, hasSocialDivision, strict gender roles]
-
A.
haveSocialDivision
chosen
Indicates that a group or society is organized into distinct social categories, classes, or divisions that differentiate its members.
-
B.
hasCivilDivision
Indicates that one administrative or political entity is subdivided into, or is associated with, a specific civil division (such as a county, district, or municipality).
-
C.
hasEthnicDivision
Indicates that a group, region, or entity is characterized by internal divisions or distinctions based on ethnicity.
-
D.
hadInternalDivision
Indicates that an entity experienced a split or conflict within its own members, factions, or components.
-
E.
politicallyDividedInto
Indicates that a political entity is formally separated into distinct internal political units or regions.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d2f39188190976e8b6b111499a0 |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.